summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSebastien Helleu <flashcode@flashtux.org>2011-08-03 12:30:43 +0200
committerSebastien Helleu <flashcode@flashtux.org>2011-08-03 12:30:43 +0200
commitc96499c81789eff0feb61aaf562c0ddd0e39ac62 (patch)
tree2be6dd5601f1f65bbb18c2c713f8c7a3b3f2170e /doc
parent4ed5ff86fd0a8b1a0fafef3daced08f0154ae6db (diff)
downloadweechat-c96499c81789eff0feb61aaf562c0ddd0e39ac62.zip
doc: add IRC SASL authentication in user guide
Diffstat (limited to 'doc')
-rw-r--r--doc/de/weechat_user.de.txt27
-rw-r--r--doc/en/weechat_user.en.txt28
-rw-r--r--doc/fr/weechat_user.fr.txt28
-rw-r--r--doc/it/weechat_user.it.txt27
4 files changed, 104 insertions, 6 deletions
diff --git a/doc/de/weechat_user.de.txt b/doc/de/weechat_user.de.txt
index b68daee36..826f08126 100644
--- a/doc/de/weechat_user.de.txt
+++ b/doc/de/weechat_user.de.txt
@@ -1241,6 +1241,31 @@ $ cat nick.cer nick.key > ~/.weechat/ssl/nick.pem
Für weiterreichende Informationen lesen Sie bitte: http://www.oftc.net/oftc/NickServ/CertFP
+// TRANSLATION MISSING
+[[irc_sasl_authentication]]
+SASL authentication
+^^^^^^^^^^^^^^^^^^^
+
+WeeChat supports SASL authentication, using two mechanisms: "plain" (default)
+or "dh-blowfish" (crypted password).
+
+Options in servers are:
+
+* 'sasl_mechanism': mechanism to use ("plain" or "dh-blowfish")
+* 'sasl_timeout': timeout (in seconds) for authentication
+* 'sasl_username': username
+* 'sasl_password': password
+
+If you want to use "dh-blowfish" by default for all servers:
+
+----------------------------------------
+/set irc.server_default.sasl_mechanism dh-blowfish
+----------------------------------------
+
+[NOTE]
+The "gcrypt" library required when compiling WeeChat in order to use
+"dh-blowfish" mechanism (see <<dependencies,dependencies>>).
+
[[irc_tor_freenode]]
Verbindung zu Freenode mittels TOR/SASL herstellen
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -1251,7 +1276,7 @@ Dies dient dazu die eigene Privatsphäre und Sicherheit im Internet zu erhöhen.
Zuerst sollte man sicher gehen, dass WeeChat mit <<dependencies,libgcrypt11-dev>> kompiliert
wurde (sofern WeeChat aus den Quellen erstellt wurde); es ist nicht verpflichtend, allerdings
-bietet DH-BLOWFISH eine größere Sicherheit als eine PLAIN Authentifikation mittels SASL.
+bietet "dh-blowfish" eine größere Sicherheit als eine "plain" Authentifikation mittels SASL.
Im ersten Schritt muss TOR installiert werden. Für Debian (und Derivate):
diff --git a/doc/en/weechat_user.en.txt b/doc/en/weechat_user.en.txt
index 92640ba49..b7b8e1657 100644
--- a/doc/en/weechat_user.en.txt
+++ b/doc/en/weechat_user.en.txt
@@ -1222,6 +1222,30 @@ $ cat nick.cer nick.key > ~/.weechat/ssl/nick.pem
For more information, look at http://www.oftc.net/oftc/NickServ/CertFP
+[[irc_sasl_authentication]]
+SASL authentication
+^^^^^^^^^^^^^^^^^^^
+
+WeeChat supports SASL authentication, using two mechanisms: "plain" (default)
+or "dh-blowfish" (crypted password).
+
+Options in servers are:
+
+* 'sasl_mechanism': mechanism to use ("plain" or "dh-blowfish")
+* 'sasl_timeout': timeout (in seconds) for authentication
+* 'sasl_username': username
+* 'sasl_password': password
+
+If you want to use "dh-blowfish" by default for all servers:
+
+----------------------------------------
+/set irc.server_default.sasl_mechanism dh-blowfish
+----------------------------------------
+
+[NOTE]
+The "gcrypt" library required when compiling WeeChat in order to use
+"dh-blowfish" mechanism (see <<dependencies,dependencies>>).
+
[[irc_tor_freenode]]
Connect to Freenode with TOR/SASL
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -1231,8 +1255,8 @@ In addition to SSL, Freenode servers support connections with TOR
and groups to improve their privacy and security on the Internet.
First, make sure to have WeeChat compiled with <<dependencies,libgcrypt11-dev>>
-(if built from sources); it's not mandatory, but DH-BLOWFISH ensures stronger
-security compared to PLAIN authentication system with SASL.
+(if built from sources); it's not mandatory, but "dh-blowfish" ensures stronger
+security compared to "plain" authentication system with SASL.
In first place, install TOR. For Debian (and derivated):
diff --git a/doc/fr/weechat_user.fr.txt b/doc/fr/weechat_user.fr.txt
index 96e8c6b9d..d0c7d0842 100644
--- a/doc/fr/weechat_user.fr.txt
+++ b/doc/fr/weechat_user.fr.txt
@@ -1258,6 +1258,30 @@ $ cat nick.cer nick.key > ~/.weechat/ssl/nick.pem
Pour plus d'informations, consulter http://www.oftc.net/oftc/NickServ/CertFP
+[[irc_sasl_authentication]]
+Authentification avec SASL
+^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+WeeChat supporte l'authentification avec SASL, en utilisant deux mécanismes :
+"plain" (par défaut) ou "dh-blowfish" (mot de passe chiffré).
+
+Les options dans le serveur sont :
+
+* 'sasl_mechanism' : mécanisme à utiliser ("plain" ou "dh-blowfish")
+* 'sasl_timeout' : délai d'attente maximum (en secondes) pour l'authentification
+* 'sasl_username' : nom d'utilisateur
+* 'sasl_password' : mot de passe
+
+Si vous voulez utiliser "dh-blowfish" par défaut pour tous les serveurs :
+
+----------------------------------------
+/set irc.server_default.sasl_mechanism dh-blowfish
+----------------------------------------
+
+[NOTE]
+La librairie "gcrypt" est requise lors de la compilation de WeeChat pour
+utiliser le mécanisme "dh-blowfish" (voir <<dependencies,les dépendances>>).
+
[[irc_tor_freenode]]
Connexion à Freenode avec TOR/SASL
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -1268,8 +1292,8 @@ personnes et groupes d'améliorer leur vie privée et sécurité sur Internet.
Premièrement, assurez-vous d'avoir compilé WeeChat avec
<<dependencies,libgcrypt11-dev>> (si construit depuis les sources); ce n'est
-pas obligatoire, mais DH-BLOWFISH assure une meilleure sécurité comparé à
-l'authentification PLAIN avec SASL.
+pas obligatoire, mais "dh-blowfish" assure une meilleure sécurité comparé à
+l'authentification "plain" avec SASL.
En premier lieu, installez TOR. Pour Debian (et dérivés) :
diff --git a/doc/it/weechat_user.it.txt b/doc/it/weechat_user.it.txt
index bcbf4c44d..d3a5eb3fc 100644
--- a/doc/it/weechat_user.it.txt
+++ b/doc/it/weechat_user.it.txt
@@ -1247,6 +1247,31 @@ $ cat nick.cer nick.key > ~/.weechat/ssl/nick.pem
Per maggiori informazioni consultare http://www.oftc.net/oftc/NickServ/CertFP
+// TRANSLATION MISSING
+[[irc_sasl_authentication]]
+SASL authentication
+^^^^^^^^^^^^^^^^^^^
+
+WeeChat supports SASL authentication, using two mechanisms: "plain" (default)
+or "dh-blowfish" (crypted password).
+
+Options in servers are:
+
+* 'sasl_mechanism': mechanism to use ("plain" or "dh-blowfish")
+* 'sasl_timeout': timeout (in seconds) for authentication
+* 'sasl_username': username
+* 'sasl_password': password
+
+If you want to use "dh-blowfish" by default for all servers:
+
+----------------------------------------
+/set irc.server_default.sasl_mechanism dh-blowfish
+----------------------------------------
+
+[NOTE]
+The "gcrypt" library required when compiling WeeChat in order to use
+"dh-blowfish" mechanism (see <<dependencies,dependencies>>).
+
[[irc_tor_freenode]]
Connessione a Freenode con TOR/SASL
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -1257,7 +1282,7 @@ utenti e gruppi di migliorare la propria privacy e la sicurezza su Internet.
Per prima cosa, assicurarsi che WeeChat sia compilato con
<<dependencies,libgcrypt11-dev>> (se compilato da sorgenti); non è
-obbligatorio, ma DH-BLOWFISH assicura una maggiore sicurezza rispetto al
+obbligatorio, ma "dh-blowfish" assicura una maggiore sicurezza rispetto al
sistema di autenticazione con SASL.
Il primo passo consiste nell'installare TOR. Per Debian (e derivate):