[Pkg-privacy-commits] [libotr] 32/225: * Protocol-v2.html: Fix a typo, and correct the documentation regarding when MAC keys are revealed.

[Ximin Luo]

This is an automated email from the git hooks/post-receive script.

infinity0 pushed a commit to branch master
in repository libotr.

commit 58fd90cb77c836ff9fa762e91d2b2becc6d5aae8
Author: cypherpunk <cypherpunk>
Date:   Fri May 12 14:14:17 2006 +0000

    	* Protocol-v2.html: Fix a typo, and correct the documentation
    	regarding when MAC keys are revealed.
---
 ChangeLog        |  5 +++++
 Protocol-v2.html | 13 +++++++------
 2 files changed, 12 insertions(+), 6 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 6d6bb2a..862ec5f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2006-05-09
+
+	* Protocol-v2.html: Fix a typo, and correct the documentation
+	regarding when MAC keys are revealed.
+
 2006-04-13
 
 	* src/context.h: Change "struct fingerprint" to "struct
diff --git a/Protocol-v2.html b/Protocol-v2.html
index b24dad0..8c001e9 100644
--- a/Protocol-v2.html
+++ b/Protocol-v2.html
@@ -178,7 +178,7 @@ receiving AES key, ek, and the receiving MAC key, mk, as detailed
 below.  (These will be the same as the keys Alice generated, above.)</li>
 <li>Uses mk to verify MAC<sub>mk</sub>(T<sub>A</sub>).</li>
 <li>Uses ek and ctr to decrypt
-AES-CTR<sub>ek,ctr</sub>(T<sub>A</sub>).</li>
+AES-CTR<sub>ek,ctr</sub>(msg).</li>
 </ol>
 </li>
 </ul>
@@ -690,12 +690,13 @@ receiving AES key.</li>
 </ul>
 <h4>Revealing MAC keys</h4>
 <p>Whenever you are about to forget either one of your old D-H key pairs, or
-one of your correspondent's old D-H public keys, take all of the MAC keys
-that were generated by that key (note that there are up to four: the
-sending and receiving MAC keys produced by the pairings of that key with
+one of your correspondent's old D-H public keys, take all of the
+receiving MAC keys
+that were generated by that key (note that there are up to two: the
+receiving MAC keys produced by the pairings of that key with
 each of two of the other side's keys; but note that you only need to
-take MAC keys that were actually used to either create a MAC on a
-message, or verify a MAC on a message), and put them (as a set of
+take MAC keys that were actually used to verify a MAC on a message), and
+put them (as a set of
 concatenated 20-byte values) into the "Old MAC keys to be revealed"
 section of the next Data Message you send.  This in done to allow the
 forgeability of OTR transcripts: once the MAC keys are revealed, anyone

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-privacy/packages/libotr.git