pegasus/weechat
1
0
Fork 0
mirror of https://github.com/weechat/weechat.git synced 2026-06-25 04:16:38 +02:00
Code Activity

doc: add IRC SASL "dh-aes" mechanism in user's guide

Browse Source
This commit is contained in:
Sebastien Helleu
2013-05-01 10:02:11 +02:00
parent 1c4e3c0e84
commit ebcea798bb
5 changed files with 55 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/de/weechat_user.de.txt
+13 -6
View File
@@ -91,7 +91,8 @@ welche Pakete optional genutzt werden können.
| libncursesw5-dev ^(2)^ | | *ja* | ncurses Oberfläche
| libcurl4-gnutls-dev | | *ja* | URL Transfer
| zlib1g-dev | | *ja* | Kompression für Pakete, die mittels Relay- (WeeChat Protokoll), Script-Erweiterung übertragen werden
| libgcrypt11-dev | | *ja* | SASL Authentifikation am IRC Server mittels DH-BLOWFISH Methode, Script-Erweiterung
// TRANSLATION MISSING
| libgcrypt11-dev | | *ja* | IRC SASL authentication (DH-BLOWFISH/DH-AES), Script-Erweiterung
| libgnutls-dev | ≥ 2.2.0 | | SSL Verbindung zu einem IRC Server, Unterstützung von SSL in der Relay-Erweiterung
| gettext | | | Internationalisierung (Übersetzung der Mitteilungen; Hauptsprache ist englisch)
| ca-certificates | | | Zertifikate für SSL Verbindungen
@@ -1834,14 +1835,20 @@ Für weiterreichende Informationen lesen Sie bitte: http://www.oftc.net/oftc/Nic
SASL Authentifizierung
^^^^^^^^^^^^^^^^^^^^^^
WeeChat unterstützt drei mögliche Verfahren bei einer SASL Authentifikation:
"plain" (Passwort liegt in Klarschrift vor), "dh-blowfish" (Passwort wird verschlüsselt)
oder "external" (SSL Zertifikat welches auf Client Seite vorliegt)
// TRANSLATION MISSING
WeeChat supports SASL authentication, using different mechanisms:
* 'plain': Passwort liegt in Klarschrift vor
// TRANSLATION MISSING
* 'dh-blowfish': blowfish encrypted password
// TRANSLATION MISSING
* 'dh-aes': AES encrypted password
* 'external': SSL Zertifikat welches auf Client Seite vorliegt
Optionen für Server sind:
* 'sasl_mechanism': Mechanismus welcher genutzt werden soll ("plain",
"dh-blowfish" oder "external")
// TRANSLATION MISSING
* 'sasl_mechanism': Mechanismus welcher genutzt werden soll (see above)
* 'sasl_timeout': Zeitüberschreitung für Authentifizierung (in Sekunden)
* 'sasl_username': Username (Nickname)
* 'sasl_password': Passwort
doc/en/weechat_user.en.txt
+9 -6
View File
@@ -91,7 +91,7 @@ compile WeeChat.
| libncursesw5-dev ^(2)^ | | *yes* | ncurses interface
| libcurl4-gnutls-dev | | *yes* | URL transfer
| zlib1g-dev | | *yes* | compression of packets in relay plugin (weechat protocol), script plugin
| libgcrypt11-dev | | *yes* | SASL authentication with IRC server using DH-BLOWFISH mechanism, script plugin
| libgcrypt11-dev | | *yes* | IRC SASL authentication (DH-BLOWFISH/DH-AES), script plugin
| libgnutls-dev | ≥ 2.2.0 | | SSL connection to IRC server, support of SSL in relay plugin
| gettext | | | internationalization (translation of messages; base language is English)
| ca-certificates | | | certificates for SSL connections
@@ -1800,13 +1800,16 @@ For more information, look at http://www.oftc.net/oftc/NickServ/CertFP
SASL authentication
^^^^^^^^^^^^^^^^^^^
WeeChat supports SASL authentication, using three mechanisms: "plain" (plain
text password), "dh-blowfish" (encrypted password) or "external" (client side
SSL cert).
WeeChat supports SASL authentication, using different mechanisms:
* 'plain': plain text password
* 'dh-blowfish': blowfish encrypted password
* 'dh-aes': AES encrypted password
* 'external': client side SSL cert
Options in servers are:
* 'sasl_mechanism': mechanism to use ("plain", "dh-blowfish" or "external")
* 'sasl_mechanism': mechanism to use (see above)
* 'sasl_timeout': timeout (in seconds) for authentication
* 'sasl_username': username (nick)
* 'sasl_password': password
@@ -1819,7 +1822,7 @@ If you want to use "dh-blowfish" by default for all servers:
[NOTE]
The "gcrypt" library is required when compiling WeeChat in order to use
"dh-blowfish" mechanism (see <<dependencies,dependencies>>).
"dh-blowfish" and "dh-aes" mechanisms (see <<dependencies,dependencies>>).
[[irc_tor_freenode]]
Connect to Freenode with TOR/SASL
doc/fr/weechat_user.fr.txt
+9 -5
View File
@@ -93,7 +93,7 @@ compiler WeeChat.
| libncursesw5-dev ^(2)^ | | *oui* | interface ncurses
| libcurl4-gnutls-dev | | *oui* | transfert d'URL
| zlib1g-dev | | *oui* | compression des paquets dans l'extension relay (protocole weechat), extension script
| libgcrypt11-dev | | *oui* | authentification SASL avec le serveur IRC, en utilisant le mécanisme DH-BLOWFISH, extension script
| libgcrypt11-dev | | *oui* | authentification IRC SASL (DH-BLOWFISH/DH-AES), extension script
| libgnutls-dev | ≥ 2.2.0 | | connexion SSL au serveur IRC, support SSL dans l'extension relay
| gettext | | | internationalisation (traduction des messages; la langue de base est l'anglais)
| ca-certificates | | | certificats pour les connexions SSL
@@ -1863,13 +1863,17 @@ Pour plus d'informations, consulter http://www.oftc.net/oftc/NickServ/CertFP
Authentification avec SASL
^^^^^^^^^^^^^^^^^^^^^^^^^^
WeeChat supporte l'authentification avec SASL, en utilisant trois mécanismes :
"plain" (mot de passe en clair), "dh-blowfish" (mot de passe chiffré) ou
"external" (certificat SSL côté client).
WeeChat supporte l'authentification avec SASL, en utilisant différents
mécanismes :
* 'plain' : mot de passe en clair
* 'dh-blowfish' : mot de passe chiffré avec blowfish
* 'dh-aes' : mot de passe chiffré avec AES
* 'external' : certificat SSL côté client
Les options dans le serveur sont :
* 'sasl_mechanism' : mécanisme à utiliser ("plain", "dh-blowfish" ou "external")
* 'sasl_mechanism' : mécanisme à utiliser (voir ci-dessus)
* 'sasl_timeout' : délai d'attente maximum (en secondes) pour l'authentification
* 'sasl_username' : nom d'utilisateur (pseudo)
* 'sasl_password' : mot de passe
doc/it/weechat_user.it.txt
+12 -5
View File
@@ -97,7 +97,7 @@ compilare WeeChat.
// TRANSLATION MISSING
| zlib1g-dev | | *sì* | compression of packets in relay plugin (weechat protocol), script plugin
// TRANSLATION MISSING
| libgcrypt11-dev | | *sì* | autenticazione SASL per i server IRC che utilizzano il meccanismo DH-BLOWFISH, script plugin
| libgcrypt11-dev | | *sì* | IRC SASL authentication (DH-BLOWFISH/DH-AES), script plugin
// TRANSLATION MISSING
| libgnutls-dev | ≥ 2.2.0 | | connessione SSL al server IRC, support of SSL in relay plugin
| gettext | | | internazionalizzazione (traduzione dei messaggi; la lingua base è l'inglese)
@@ -1843,13 +1843,20 @@ Per maggiori informazioni consultare http://www.oftc.net/oftc/NickServ/CertFP
Autenticazione SASL
^^^^^^^^^^^^^^^^^^^
WeeChat supporta l'autenticazione SASL, usando tre meccanismi: "plain" (password
in chiaro), "dh-blowfish" (password cifrata)" o "external" (certificato SSL da
lato client).
// TRANSLATION MISSING
WeeChat supports SASL authentication, using different mechanisms:
* 'plain': password in chiaro
// TRANSLATION MISSING
* 'dh-blowfish': blowfish encrypted password
// TRANSLATION MISSING
* 'dh-aes': AES encrypted password
* 'external': certificato SSL da lato client
Le opzioni nel server sono:
* 'sasl_mechanism': meccanismo da usare ("plain", "dh-blowfish" o "external")
// TRANSLATION MISSING
* 'sasl_mechanism': meccanismo da usare (see above)
* 'sasl_timeout': timeout (in secondi) per l'autenticazione
* 'sasl_username': nome utente (nick)
* 'sasl_password': password
doc/ja/weechat_user.ja.txt
+12 -5
View File
@@ -83,7 +83,8 @@ WeeChat は cmake または autotools を使ってコンパイルできます (c
| libncursesw5-dev ^(2)^ | | *yes* | ncurses インターフェイス
| libcurl4-gnutls-dev | | *yes* | URL 転送
| zlib1g-dev | | *yes* | relay プラグインでパケットを圧縮 (weechat プロトコル)、スクリプトプラグイン
| libgcrypt11-dev | | *yes* | DH-BLOWFISH メカニズムを用いた IRC サーバ用の SASL 認証、スクリプトプラグイン
// TRANSLATION MISSING
| libgcrypt11-dev | | *yes* | IRC SASL authentication (DH-BLOWFISH/DH-AES), script plugin
| libgnutls-dev | ≥ 2.2.0 | | IRC サーバへの SSL 接続
| gettext | | | 国際化 (メッセージの翻訳; ベース言語は英語です)
| ca-certificates | | | SSL 接続に必要な証明書、relay プラグインで SSL サポート
@@ -1733,13 +1734,19 @@ $ openssl req -nodes -newkey rsa:2048 -keyout nick.pem -x509 -days 365 -out nick
[[irc_sasl_authentication]]
==== SASL 認証 ====
WeeChat は SASL 認証をサポートしています。認証アルゴリズムは "plain"
(平文パスワード)、"dh-blowfish" (暗号化パスワード)、"external"
(クライアント側 SSL 証明書) の 3 つです。
// TRANSLATION MISSING
WeeChat supports SASL authentication, using different mechanisms:
// TRANSLATION MISSING
* 'plain': plain text password
* 'dh-blowfish': blowfish encrypted password
* 'dh-aes': AES encrypted password
* 'external': client side SSL cert
サーバオプション:
* 'sasl_mechanism': 利用する認証メカニズム ("plain"、"dh-blowfish"、"external")
// TRANSLATION MISSING
* 'sasl_mechanism': 利用する認証メカニズム (see above)
* 'sasl_timeout': 認証時のタイムアウト (秒単位)
* 'sasl_username': ユーザ名 (ニックネーム)
* 'sasl_password': パスワード