[pkg-otr-team] [irssi-plugin-otr] 91/167: Add help files to git repo
Holger Levsen
holger at moszumanska.debian.org
Mon Mar 3 21:55:35 UTC 2014
This is an automated email from the git hooks/post-receive script.
holger pushed a commit to tag 4.0.0
in repository irssi-plugin-otr.
commit f1c91a8bec6b17e54c60383968be70496f788983
Author: Ian Goldberg <iang at cs.uwaterloo.ca>
Date: Mon May 28 14:43:34 2012 -0400
Add help files to git repo
---
help/auth-ans.png | Bin 0 -> 35336 bytes
help/auth-mf.png | Bin 0 -> 50157 bytes
help/auth-qa.png | Bin 0 -> 35657 bytes
help/auth-ss.png | Bin 0 -> 33183 bytes
help/authenticate-dialog.png | Bin 0 -> 22430 bytes
help/authenticate-error.png | Bin 0 -> 18897 bytes
help/authenticate-fail.png | Bin 0 -> 18175 bytes
help/authenticate-success.png | Bin 0 -> 18626 bytes
help/authenticate.php | 133 +++++++++++++++++++++++
help/authenticate_fr.php | 146 +++++++++++++++++++++++++
help/badsecret.png | Bin 0 -> 21443 bytes
help/conv-empty.png | Bin 0 -> 13381 bytes
help/conv-menuauthenticate.png | Bin 0 -> 35745 bytes
help/conv-otrmenu.png | Bin 0 -> 25379 bytes
help/conv-private.png | Bin 0 -> 35651 bytes
help/conv-unauthenticated.png | Bin 0 -> 30970 bytes
help/fingerprint-dialog.png | Bin 0 -> 30205 bytes
help/fingerprint.php | 44 ++++++++
help/finished-button.png | Bin 0 -> 1376 bytes
help/goodsecret.png | Bin 0 -> 23840 bytes
help/levels.php | 46 ++++++++
help/levels_fr.php | 43 ++++++++
help/main.css | 220 ++++++++++++++++++++++++++++++++++++++
help/notprivate-ab.png | Bin 0 -> 10458 bytes
help/notprivate-button.png | Bin 0 -> 1586 bytes
help/private-ab.png | Bin 0 -> 10358 bytes
help/private-button.png | Bin 0 -> 1303 bytes
help/progress-error.png | Bin 0 -> 16999 bytes
help/progress-failed.png | Bin 0 -> 16692 bytes
help/progress-success-maywant.png | Bin 0 -> 22794 bytes
help/progress-success.png | Bin 0 -> 18951 bytes
help/unrecognized.png | Bin 0 -> 24679 bytes
help/unverified-ab.png | Bin 0 -> 10168 bytes
help/unverified-button.png | Bin 0 -> 1429 bytes
help/unverified.php | 1 +
35 files changed, 633 insertions(+)
diff --git a/help/auth-ans.png b/help/auth-ans.png
new file mode 100644
index 0000000..75742b5
Binary files /dev/null and b/help/auth-ans.png differ
diff --git a/help/auth-mf.png b/help/auth-mf.png
new file mode 100644
index 0000000..e87b95c
Binary files /dev/null and b/help/auth-mf.png differ
diff --git a/help/auth-qa.png b/help/auth-qa.png
new file mode 100644
index 0000000..33c60c3
Binary files /dev/null and b/help/auth-qa.png differ
diff --git a/help/auth-ss.png b/help/auth-ss.png
new file mode 100644
index 0000000..472ad0c
Binary files /dev/null and b/help/auth-ss.png differ
diff --git a/help/authenticate-dialog.png b/help/authenticate-dialog.png
new file mode 100644
index 0000000..4fc0a75
Binary files /dev/null and b/help/authenticate-dialog.png differ
diff --git a/help/authenticate-error.png b/help/authenticate-error.png
new file mode 100644
index 0000000..8248c07
Binary files /dev/null and b/help/authenticate-error.png differ
diff --git a/help/authenticate-fail.png b/help/authenticate-fail.png
new file mode 100644
index 0000000..0a77756
Binary files /dev/null and b/help/authenticate-fail.png differ
diff --git a/help/authenticate-success.png b/help/authenticate-success.png
new file mode 100644
index 0000000..aad11aa
Binary files /dev/null and b/help/authenticate-success.png differ
diff --git a/help/authenticate.php b/help/authenticate.php
new file mode 100644
index 0000000..87c627e
--- /dev/null
+++ b/help/authenticate.php
@@ -0,0 +1,133 @@
+<?php
+
+if ($_REQUEST['lang'] == 'fr') {
+ include('authenticate_fr.php');
+} else { ?>
+<html><head>
+<title>Off-the-Record Messaging: Authentication</title>
+<link rel="stylesheet" type="text/css" href="main.css" />
+</head>
+<body><h1>Off-the-Record Messaging</h1>
+<h2>Authentication</h2>
+<p>You've probably received email from people pretending to be banks, credit
+agencies, even wealthy Nigerian expatriates. People lie about who they
+are all the time on the Internet. <b>Authentication</b> is a way to make
+sure that nobody can lie to you about who they are when they use OTR.
+</p>
+<h3>When to authenticate</h3>
+<p>You should authenticate a buddy the very first time that you talk to
+them using OTR. If you don't, then you can't really be sure that
+someone else isn't impersonating them or trying to listen in on your
+conversation. However, once you've authenticated your buddy, you
+don't have to do it again. OTR will automatically do the authentication
+for all of your future conversations with that buddy.
+</p>
+<p>The only exceptions occur when your buddy switches between multiple
+computers or multiple IM accounts. In this case, you will need to
+authenticate once for each computer and account. Once you've done this,
+your buddy can freely use any of the computers you've authenticated them
+on, and OTR will recognize them automatically. If your buddy uses
+a new computer or account that OTR does not recognize, a message will pop up
+in your conversation window telling you about it:
+</p>
+<br /><img src="conv-unauthenticated.png" />
+<h3>How to authenticate</h3>
+<p>OTR provides three ways to authenticate your buddy:</p>
+<ol><li>Question and answer</li>
+<li>Shared secret</li>
+<li>Manual fingerprint verification</li></ol>
+
+<p>To start the authentication process, you need to first be
+communicating with your buddy in the "Unverified" or "Private"
+states. [Note that the "Private" state indicates that you have
+already successfully authenticated your buddy, and it is not
+necessary to do it again.] Choose "Authenticate buddy" from the OTR
+menu.</p>
+<br /><img src="conv-menuauthenticate.png" />
+<p>The Authenticate Buddy dialog will pop up. Use the combo box
+to select which of the three authentication methods you would like
+to use.</p>
+
+<h4>Question and answer</h4>
+<img src="auth-qa.png" />
+<p>To authenticate using a question, pick a question whose answer is
+known only to you and your buddy. Enter this question and this
+answer, then wait for your buddy to enter the answer too. If the
+answers don't match, then either your buddy made a mistake typing in the
+answer, or you may be talking to an imposter.</p>
+
+<p>If your buddy answers correctly, then you have successfully
+authenticated him or her, and the OTR status of this conversation
+will change to "Private".</p>
+
+<p>Your buddy will probably also want to ask you a question as well in
+order for him or her to authenticate you back.</p>
+
+<p>Note that this method first appeared in pidgin-otr 3.2.0; if your
+buddy is using an older version, this will not work.</p>
+
+<h4>Shared secret</h4>
+<img src="auth-ss.png" />
+<p>To authenticate someone with the shared secret method, you and your
+buddy should decide on a secret word or phrase in advance. This can
+be done however you like, but you shouldn't type the phrase directly
+into your conversation.</p>
+
+<p>Enter the shared secret into the field provided in the Authenticate
+Buddy dialog box. Once you enter the secret and hit OK, your buddy
+will be asked to do exactly the same thing. If you both enter the
+same text, then OTR will accept that you are really talking to your
+buddy. Otherwise, OTR reports that authentication has failed. This
+either means that your buddy made a mistake typing in the text, or
+it may mean that someone is intercepting your communication.</p>
+
+<p>Note that this method first appeared in pidgin-otr 3.1.0; if your
+buddy is using an older version, this will not work.</p>
+
+<h4>Manual fingerprint verification</h4>
+<img src="auth-mf.png" />
+<p>If your buddy is using a version of pidgin-otr before 3.1.0, or a
+different OTR client that does not support the other authentication
+methods, you will need to use manual fingerprint verification.</p>
+
+<p>You will need some other authenticated communication channel (such
+as speaking to your buddy on the telephone, or sending gpg-signed
+messages). You should tell each other your own fingerprints. If
+the fingerprint your buddy tells you matches the one listed as his
+or her "purported fingerprint", pull down the selection that says "I
+have not" (verified that this is in fact the correct fingerprint),
+and change it to "I have".</p>
+
+<p>Once you do this, the OTR status will change to "Private". Note
+that you only need to do this once per buddy (or once per
+fingerprint, if your buddy has more than one fingerprint).
+pidgin-otr will remember which fingerprints you have marked as
+verified.</p>
+
+<h3>What the results mean</h3>
+<p>When you have entered your secret and hit OK, a progress bar pops up. This
+bar should fill up to 100% and then display one of the following messages:
+</p>
+<br /><img src="progress-success.png" />
+<p>This means that authentication has been a complete success.
+The OTR button will automatically change to "Private", showing that
+conversations with this buddy are safe.
+</p>
+<br /><img src="progress-failed.png" />
+<p>This means that although there were no errors, your buddy did not enter
+the same text as you. You should try again, making sure that you are clear
+about what to type (for example, "the restaurant name <em>in lower case</em>").
+If you repeatedly get this result, you should not trust that your buddy is who you think he or she is.
+</p>
+<br /><img src="progress-error.png" />
+<p>This means that something has gone wrong and the process could not complete
+normally. This will happen if your buddy hits "cancel" or fails to receive
+one of your messages. In this case, you should simply try again. If you try
+several times and keep getting an error, you should not trust that your buddy is who you think he or she is.
+</p>
+<br /><img src="progress-success-maywant.png" />
+<p>This means that you answered your buddy's authentication question successfully, so you have authenticated yourself to your buddy. However, your buddy has not yet authenticated to you. You may want to ask your buddy an authentication question by selecting "Authenticate buddy" from the OTR menu yourself.
+</p>
+</body></html>
+
+<?php } ?>
diff --git a/help/authenticate_fr.php b/help/authenticate_fr.php
new file mode 100644
index 0000000..a5102ed
--- /dev/null
+++ b/help/authenticate_fr.php
@@ -0,0 +1,146 @@
+<?php header('Content-Type: text/html; charset=UTF-8');?>
+<html><head>
+<title>Messagerie Off-the-Record : Authentification</title>
+<link rel="stylesheet" type="text/css" href="main.css" />
+</head>
+<body><h1>Messagerie Off-the-Record</h1>
+<h2>Authentification</h2>
+<p>Vous avez probablement déjà reçu des emails de gens prétendant être
+une banque, une agence de crédit, ou un expatrié nigérien. Sur
+internet, les gens mentent tout le temps au sujet de leur
+identité. L'<b>authentification</b> est une manière de s'assurer que
+votre interlocuteur est bien celui qu'il prétend être lorsqu'il
+utilise OTR.
+</p>
+<h3>Quand s'authentifier ?</h3>
+<p>Vous devriez authentifier chaque contact la première fois que vous
+lui parlez en utilisant OTR. Si vous ne le faites pas, il y a deux
+risques : un imposteur peut se faire passer pour la personne à
+qui vous pensez parler, ou bien quelqu'un peut écouter votre
+conversation. Lorsque vous aurez authentifié votre interlocuteur, vous
+n'aurez pas à le refaire : OTR assurera automatiquement
+l'authentification lors de toutes vos conversations suivantes avec ce
+contact.
+</p>
+<p>Les seules exceptions se produisent lorsque votre contact change
+d'ordinateur ou de compte de messagerie instantanée. Dans ce cas, vous
+devrez l'authentifier une nouvelle fois pour chaque ordinateur et
+chaque compte. Lorsque vous l'aurez fait, votre contact pourra passer
+d'un ordinateur à l'autre et OTR le reconnaîtra automatiquement. Si
+votre contact utilise un nouvel ordinateur ou un compte qu'OTR ne
+connaît pas encore, un message surgira dans votre fenêtre de dialogue
+vous disant :
+</p>
+<br /><img src="conv-unauthenticated.png" />
+<h3>Comment authentifier ?</h3>
+<p>OTR fournit trois moyens d'authentifier vos contacts :</p>
+<ol><li>Question-réponse</li>
+<li>Secret partagé</li>
+<li>Vérification manuelle de l'empreinte</li></ol>
+
+<p>Pour commencer l'authentification, vous devez lancer un dialogue
+"Non-privé" ou "Privé". [Notez que le statut "Privé" indique que vous
+avez déjà authentifié votre contact, et qu'il est superflu de le
+refaire.] Choisissez "Authentifier contact" dans le menu OTR.</p>
+<br /><img src="conv-menuauthenticate.png" />
+<p>Une fenêtre "Authentifier contact" surgira alors. Utilisez le menu
+déroulant pour choisir lequel des trois moyens d'authentification vous
+utiliserez.</p>
+
+<h4>Question-réponse</h4>
+<img src="auth-qa.png" />
+<p>Pour authentifier votre interlocuteur en utilisant une question,
+choisissez une question dont seuls lui et vous connaissez la
+réponse. Écrivez cette question et sa réponse, puis attendez que votre
+contact donne la réponse adéquate. Si vos réponses ne sont pas
+identiques, alors soit c'est une question d'orthographe, soit vous
+parlez à un imposteur.</p>
+
+<p>Si votre contact répond correctement, alors vous l'avez authentifié
+avec succès, et le statut OTR de la conversation deviendra
+"Privé".</p>
+
+<p>Votre contact voudra probablement, lui aussi, vous poser une
+question afin de vous authentifier à son tour.</p>
+
+<p>Notez que cette méthode est apparue dans pidgin-otr 3.2.0 ; si
+votre contact utilise une version plus ancienne, cela ne fonctionnera
+pas.
+
+<h4>Secret partagé</h4>
+<img src="auth-ss.png" />
+<p>Pour authentifier quelqu'un avec la méthode du secret partagé, vous
+et votre contact devez décider à l'avance d'un mot ou d'une phrase de
+passe. Cela peut se faire de la façon qui vous convient, mais vous ne
+devriez pas écrire cette phrase dans votre fenêtre de dialogue.</p>
+
+<p>Écrivez le secret dans la boîte prévue à cet effet de la fenêtre
+"Authentifier contact". Lorsque vous validerez, il sera demandé à
+votre contact d'écrire le secret à son tour. Si vous écrivez tous deux
+le même texte, alors OTR considèrera que vous parlez bien à votre
+contact. Autrement, OTR vous dira que l'authentification a
+échoué. Cela signifiera que l'un de vous a fait une faute
+d'orthographe, ou que quelqu'un intercepte votre communication.</p>
+
+<p>Notez que cette méthode est apparue dans pidgin-otr 3.1.0 ; si
+votre contact utilise une version plus ancienne, cela ne fonctionnera
+pas.
+
+<h4>Vérification manuelle d'empreinte</h4>
+<img src="auth-mf.png" />
+<p>Si votre contact utilise une version de pidgin-otr antérieure à la
+3.1.0, ou un client OTR qui ne propose pas les autres méthodes
+d'authentification, vous devrez utiliser la vérification manuelle
+d'empreinte.</p>
+
+<p>Vous devrez disposer d'un autre moyen de communication authentifié
+(comme parler à votre contact au téléphone, ou échanger des emails
+signés avec GnuPG). Vous devrez alors dicter (ou envoyer) vos empreintes
+respectives. Si l'empreinte que vous dicte / envoie votre contact est
+identique à celle affichée comme "empreinte prétendue pour votre
+contact", sélectionnez "Je n'ai pas" (vérifié que c'est en effet la
+bonne empreinte pour mon contact) et changez-le pour "J'ai", puis
+cliquez "Authentifier".</p>
+
+<p>Lorsque c'est fait, le statut OTR de la conversation deviendra
+"Privé". Notez qu'il vous suffit de le faire une fois pour chaque
+contact (ou une fois pour chaque empreinte, si votre contact a
+plusieurs empreintes). pidgin-otr se rappellera quelles empreintes
+vous avez marquées comme vérifiées.</p>
+
+<h3>Que signifie le résultat ?</h3>
+<p>Lorsque vous écrivez votre secret et cliquez sur
+"Authentification", une barre de progression surgit. Une fois qu'elle
+est remplie à 100%, elle affichera l'un des messages suivants :
+</p>
+<br /><img src="progress-success.png" />
+<p>Cela signifie que l'authentification a réussi. Le bouton OTR
+devient automatiquement "Privé", signe que vos conversations avec ce
+contact sont bien confidentielles.
+</p>
+<br /><img src="progress-failed.png" />
+<p>Cela signifie que, bien qu'il n'y ait pas eu d'erreur technique,
+votre contact n'a pas écrit le même texte que vous. Vous devez
+réessayer, en vous assurant que vous êtes bien d'accord sur le secret
+à écrire (par exemple "le nom du restaurant <em>en
+minuscules</em>"). Si vous recevez encore le même résultat, il n'y a
+aucune certitude que votre interlocuteur soit bien celui qu'il prétend
+être.
+</p>
+<br /><img src="progress-error.png" />
+<p>Cela signifie que quelque chose n'a pas fonctionné et que le
+processus ne s'est pas déroulé normalement. Cela se produira si votre
+contact clique sur "Annuler" ou s'il ne reçoit pas l'un de vos
+messages. Dans ce cas, il vous suffit de réessayer. Après plusieurs
+tentatives, si cette erreur apparaît encore, il est possible que votre
+interlocuteur ne soit pas celui qu'il prétend être.
+</p>
+<br /><img src="progress-success-maywant.png" />
+<p>Cela signifie que vous avez correctement répondu à la question de
+votre contact, et que vous êtes donc authentifié auprès de lui. Il
+faut encore qu'il s'authentifie auprès de vous. Pour cela, vous pouvez
+poser une question d'authentification en sélectionnant
+"Authentification Contact" dans le menu OTR.
+</p>
+</body></html>
+
diff --git a/help/badsecret.png b/help/badsecret.png
new file mode 100644
index 0000000..70897ac
Binary files /dev/null and b/help/badsecret.png differ
diff --git a/help/conv-empty.png b/help/conv-empty.png
new file mode 100644
index 0000000..dc5e48e
Binary files /dev/null and b/help/conv-empty.png differ
diff --git a/help/conv-menuauthenticate.png b/help/conv-menuauthenticate.png
new file mode 100644
index 0000000..fa6332e
Binary files /dev/null and b/help/conv-menuauthenticate.png differ
diff --git a/help/conv-otrmenu.png b/help/conv-otrmenu.png
new file mode 100644
index 0000000..fb2fba7
Binary files /dev/null and b/help/conv-otrmenu.png differ
diff --git a/help/conv-private.png b/help/conv-private.png
new file mode 100644
index 0000000..2668944
Binary files /dev/null and b/help/conv-private.png differ
diff --git a/help/conv-unauthenticated.png b/help/conv-unauthenticated.png
new file mode 100644
index 0000000..74e4e19
Binary files /dev/null and b/help/conv-unauthenticated.png differ
diff --git a/help/fingerprint-dialog.png b/help/fingerprint-dialog.png
new file mode 100644
index 0000000..f829da6
Binary files /dev/null and b/help/fingerprint-dialog.png differ
diff --git a/help/fingerprint.php b/help/fingerprint.php
new file mode 100644
index 0000000..be43dc6
--- /dev/null
+++ b/help/fingerprint.php
@@ -0,0 +1,44 @@
+<html><head>
+<title>Off-the-Record Messaging: Fingerprints</title>
+<link rel="stylesheet" type="text/css" href="main.css" />
+</head>
+<body><h1>Off-the-Record Messaging</h1>
+<h2>Fingerprints</h2>
+<p>You've probably received email from people pretending to be banks, credit
+agencies, even wealthy Nigerian expatriates. People lie about who they
+are all the time on the Internet. To make sure that nobody can lie about
+who they are when they use OTR, you can use <b>authentication</b>. Starting
+in version 3.1, OTR comes with a
+<a href="authenticate.php?lang=en">simple way</a> to authenticate your
+buddies.
+</p>
+<p>However, another common way to authenicate someone is through the use
+of <b>fingerprints</b>. Roughly speaking, a fingerprint is a long string
+of 40 letters and numbers that let you identify an OTR user. A typical
+fingerprint looks something like this:
+</p>
+<p align="center">2674D6A0 0B1421B1 BFC42AEC C56F3719 672437D8</p>
+<p>If you would prefer to use fingerprints to authenticate your buddies, and
+you are using OTR version 3.1, select <b>"Authenticate Connection"</b> from
+the OTR button, and then select <b>"Advanced"</b> from the regular
+authentication window. If you are using an older version of OTR, simply
+select <b>"Verify Fingerprint"</b> from the OTR button. You should see a
+screen that looks like this:
+</p>
+<br /><img src="fingerprint-dialog.png" />
+<p>Now you can see what your fingerprint is, as well as the fingerprint of
+the person you are talking to. But you still don't know if the fingerprint
+really belongs to your friend or to an imposter. To find out, you need a way
+to check the fingerprint. A simple way to do this is to phone your friend
+and ask them to read you their fingerprint off of their screen, so that you
+can check it against what you see. If the values are the same, then you know
+that you are not talking to an imposter.
+</p>
+<p>Regardless of whether you use fingerprints or the regular authentication
+method, you do not have to follow the above steps during every conversation.
+In many cases, you only need to authenticate each buddy once. A detailed
+description of when to authenticate may be found
+<a href="authenticate.php?lang=en">here.</a>
+</p>
+</body></html>
+
diff --git a/help/finished-button.png b/help/finished-button.png
new file mode 100644
index 0000000..69e0ee6
Binary files /dev/null and b/help/finished-button.png differ
diff --git a/help/goodsecret.png b/help/goodsecret.png
new file mode 100644
index 0000000..2b72215
Binary files /dev/null and b/help/goodsecret.png differ
diff --git a/help/levels.php b/help/levels.php
new file mode 100644
index 0000000..5374b98
--- /dev/null
+++ b/help/levels.php
@@ -0,0 +1,46 @@
+<?php
+
+if ($_REQUEST['lang'] == 'fr') {
+ include('levels_fr.php');
+} else { ?>
+<html><head>
+<title>Off-the-Record Messaging: Privacy Levels</title>
+<link rel="stylesheet" type="text/css" href="main.css" />
+</head>
+<body><h1>Off-the-Record Messaging</h1>
+<h2>Privacy Levels</h2>
+<p>A conversation can have one of four <b>privacy levels</b>:</p>
+<dl>
+<dt><img src="notprivate-button.png" alt="Not private" /></dt>
+<dd>Alice and Bob are communicating with no cryptographic protection;
+they are not using OTR at all. Mallory, who is watching the network,
+can read everything they are saying to each other.
+</dd><br /><img src="notprivate-ab.png" />
+<p></p>
+
+<dt><img src="private-button.png" alt="Private" /></dt>
+<dd>Alice and Bob are using OTR, and they have
+<a href="authenticate.php?lang=en">authenticated</a> each other. They
+are assured that they are actually talking to each other, and not to
+an imposter. They are also confident that no one watching the network
+can read their messages.
+</dd><br /><img src="private-ab.png" />
+<p></p>
+<dt><img src="unverified-button.png" alt="Unverified" />
+<dd>Alice and Bob are using OTR, but they have not
+<a href="authenticate.php?lang=en">authenticated</a> each other, which
+means they do not know for certain who they are talking to. It is
+<em>possible</em> that Mallory is impersonating one of them, or
+intercepting their conversation and reading everything they say to each
+other.
+</dd><br /><img src="unverified-ab.png" />
+<dt><img src="finished-button.png" alt="Finished" /></dt>
+<dd>Alice <em>was</em> talking to Bob using OTR, but Bob has decided to
+stop using it. In this level, Alice is prevented from accidentally
+sending a private message without protection, by preventing her from sending
+any further messages to Bob at all. She must explicitly either end her side
+of the private conversation, or else start a new one.
+</dd>
+</dl>
+</body></html>
+<?php } ?>
diff --git a/help/levels_fr.php b/help/levels_fr.php
new file mode 100644
index 0000000..f12a2ec
--- /dev/null
+++ b/help/levels_fr.php
@@ -0,0 +1,43 @@
+<?php header('Content-Type: text/html; charset=UTF-8');?>
+<html><head>
+<title>Messagerie Off-the-Record : Niveaux de confidentialité</title>
+<link rel="stylesheet" type="text/css" href="main.css" />
+</head>
+<body><h1>Messagerie Off-the-Record</h1>
+<h2>Niveaux de confidentialité</h2>
+<p>Une conversation peut avoir quatre <b>niveaux de confidentialité</b> différents :</p>
+<dl>
+<dt><img src="notprivate-button.png" alt="Non-privé" /></dt>
+<dd>Alice et Bob communiquent sans protection cryptographique ; ils
+n'utilisent pas du tout OTR. Mallory, qui surveille le réseau, peut
+lire tout ce qu'ils se racontent.
+</dd><br /><img src="notprivate-ab.png" />
+<p></p>
+
+<dt><img src="private-button.png" alt="Privé" /></dt>
+<dd>Alice and Bob utilisent OTR, et ils se sont
+<a href="authenticate.php?lang=fr">authentifiés</a>. Ils sont sûrs de
+se parler l'un à l'autre, et pas à un imposteur. Ils ont aussi la
+certitude qu'il ne suffit pas de surveiller le réseau pour pouvoir
+lire leurs échanges.
+</dd><br /><img src="private-ab.png" />
+<p></p>
+<dt><img src="unverified-button.png" alt="Non-vérifié" />
+<dd>Alice and Bob utilisent OTR, mais ils ne se sont pas
+<a href="authenticate.php?lang=fr">authentifiés</a>, ce qui signifie
+qu'ils ne sont pas certains de l'identité de leur interlocuteur. Il
+est <em>possible</em> que Mallory se fasse passer pour l'un d'eux, ou
+qu'il intercepte leurs échanges et lise à leur insu tout ce qu'ils se
+disent.
+</dd><br /><img src="unverified-ab.png" />
+<dt><img src="finished-button.png" alt="Fini" /></dt>
+<dd>Alice <em>parlait</em> à Bob en utilisant OTR, mais Bob a décidé
+d'arrêter de l'utiliser (il est passé en "Non-privé"). Ce niveau de
+confidentialité assure à Alice qu'elle n'enverra pas accidentellement
+un message privé sans protection : ses messages ne seront plus
+transmis du tout, à moins qu'elle ne choisisse, elle aussi, d'arrêter
+la discussion privée ou d'en commencer une nouvelle.
+</dd>
+</dl>
+</body></html>
+
diff --git a/help/main.css b/help/main.css
new file mode 100644
index 0000000..ac7bbb5
--- /dev/null
+++ b/help/main.css
@@ -0,0 +1,220 @@
+html, body, form, fieldset {
+margin: 0;
+padding: 0;
+}
+
+body {
+font: 12px Verdana, Arial, Helvetica, sans-serif;
+background: #fff url(baseimg/bg_body.png) top left repeat-x;
+text-align: left;
+margin: 10px 50px;
+line-height: 160%;
+}
+
+a:link, a:visited, a:active {
+text-decoration: none;
+padding-bottom: 1px;
+color: #838716;
+background: transparent url(baseimg/bg_a.png) bottom left repeat-x;
+}
+
+a:hover {
+text-decoration: none;color:#999;
+background: none;
+}
+
+h1 {
+font: 25px Georgia, Times, "Times New Roman", serif;
+}
+
+h2 {
+font: bold 18px Verdana, Arial, Helvetica, sans-serif;
+color: #444;
+background: transparent url(baseimg/bg_h2.png) bottom left repeat-x;
+letter-spacing: 1px;
+}
+
+h2 a, h2 a:hover {
+color: #444;
+}
+
+ul li {
+list-style-type: none;
+background: transparent url(baseimg/list_arrow.png) left center no-repeat;
+}
+
+li {
+padding-left: 1em;
+}
+
+/* ---------------------------------------- -----------------------------------------------------------*/
+#title {
+border-bottom: 1px solid #e6e6e6;
+}
+
+#title a {
+color: #000;
+background: none;
+}
+
+#nav {
+text-align: center;
+}
+
+#nav ul li {
+list-style-type: none;
+display: inline;
+}
+
+#nav ul {
+padding: 5px 0;
+margin: 0;
+background-color: #f7f7f7;
+}
+
+#nav li {
+background: none;
+padding: 0;
+}
+
+#nav li a {
+padding: 5px 15px;
+margin: 0;
+background-color: #fff;
+border-bottom: 3px solid #d5d5d5;
+font-weight: bold;
+}
+
+#otr {
+border: 1px solid #e6e6e6;
+border-width: 0 0 3px 0;
+padding: 1em 2em;
+background-color: #f7f7f7;
+}
+
+#otr dt {
+padding-left: 15px;
+background: transparent url(baseimg/dt_arrow.png) center left no-repeat;
+color: #333;
+font: bold 14px Georgia, Times, "Times New Roman", serif;
+margin: 10px 0 5px 0;
+}
+
+#otr dd {
+margin-left: 15px;
+}
+
+#news dt, #downloads dt, #faqs dt {
+font-weight: bold;
+color: #444;
+}
+
+#news, #press {
+background: #fff;
+}
+
+#news dd, #downloads dd, #faqs dd {
+margin: 5px 0 10px 0;
+}
+
+#news ul, #press ul {
+padding: 0;
+margin-left: 10px;
+}
+
+#press li {
+padding: 5px 15px;
+}
+
+#news dl {
+margin-left: 60px;
+padding-left: 15px;
+border-left: 3px solid #d5d5d5;
+}
+
+p.date {
+clear: left;
+width: 50px;
+float: left;
+margin: 0;
+font: bold 14px Trebuchet, "Trebuchet MS", Verdana, sans-serif;
+color: #444;
+text-align: right;
+}
+
+p.news_more {
+background: transparent url(baseimg/list_arrow.png) left center no-repeat;
+margin-top: 0 !important;
+margin-top: 10px;
+padding-left: 10px;
+text-align: left;
+}
+
+p.notice {
+border: 1px solid #ae1c1c;
+padding: 2px 10px;
+font-size: 10px;
+line-height: 140%;
+}
+
+#downloads, #mailing_lists, #documentation, #faqs, #footer {
+margin-top: 30px;
+}
+
+#downloads dd, #faqs dd {
+margin-left: 10px;
+}
+
+.download {
+width: 30%;
+float: left;
+
+margin-left: 4.5%;
+}
+
+.download_left {
+margin-left: 0;
+}
+
+.download h3 {
+margin: 0 0 15px 0;
+font: bold 15px Verdana, Arial, Helvetica, sans-serif;
+border-bottom: 2px solid #666;
+padding: 2px 0;
+color: #666;
+}
+
+.download ul {
+margin-left: 0;
+padding-left: 0;
+}
+
+.download li {
+padding: 5px 15px;
+}
+
+p.readme {
+background: transparent url(baseimg/bg_readme.png) center left no-repeat;
+padding: 2px 2px 2px 20px;
+letter-spacing: 1px;
+}
+
+#documentation ul {
+margin-left: 0;
+padding-left: 10px;
+}
+
+#documentation li {
+padding: 2px 15px;
+}
+
+#documentation h4 {
+font: bold 13px Verdana, Arial, Helvetica, sans-serif;
+color: #444;
+}
+
+#footer {
+padding: 10px 0 25px 0;
+background: transparent url(baseimg/bg_h2.png) left top repeat-x;
+font-weight: bold;
+}
diff --git a/help/notprivate-ab.png b/help/notprivate-ab.png
new file mode 100644
index 0000000..6c0ae76
Binary files /dev/null and b/help/notprivate-ab.png differ
diff --git a/help/notprivate-button.png b/help/notprivate-button.png
new file mode 100644
index 0000000..377e935
Binary files /dev/null and b/help/notprivate-button.png differ
diff --git a/help/private-ab.png b/help/private-ab.png
new file mode 100644
index 0000000..9ec081e
Binary files /dev/null and b/help/private-ab.png differ
diff --git a/help/private-button.png b/help/private-button.png
new file mode 100644
index 0000000..3a77574
Binary files /dev/null and b/help/private-button.png differ
diff --git a/help/progress-error.png b/help/progress-error.png
new file mode 100644
index 0000000..09f8354
Binary files /dev/null and b/help/progress-error.png differ
diff --git a/help/progress-failed.png b/help/progress-failed.png
new file mode 100644
index 0000000..d8a537d
Binary files /dev/null and b/help/progress-failed.png differ
diff --git a/help/progress-success-maywant.png b/help/progress-success-maywant.png
new file mode 100644
index 0000000..3868fee
Binary files /dev/null and b/help/progress-success-maywant.png differ
diff --git a/help/progress-success.png b/help/progress-success.png
new file mode 100644
index 0000000..3703b0e
Binary files /dev/null and b/help/progress-success.png differ
diff --git a/help/unrecognized.png b/help/unrecognized.png
new file mode 100644
index 0000000..c600ee1
Binary files /dev/null and b/help/unrecognized.png differ
diff --git a/help/unverified-ab.png b/help/unverified-ab.png
new file mode 100644
index 0000000..5d6b5bb
Binary files /dev/null and b/help/unverified-ab.png differ
diff --git a/help/unverified-button.png b/help/unverified-button.png
new file mode 100644
index 0000000..6da70f0
Binary files /dev/null and b/help/unverified-button.png differ
diff --git a/help/unverified.php b/help/unverified.php
new file mode 120000
index 0000000..a1293df
--- /dev/null
+++ b/help/unverified.php
@@ -0,0 +1 @@
+levels.php
\ No newline at end of file
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-otr/packages/irssi-plugin-otr.git
More information about the Pkg-otr-team
mailing list