[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[minion-cvs] Correct typos and omissions (thanks to PJM)
Update of /home/minion/cvsroot/doc
In directory moria.seul.org:/tmp/cvs-serv26620
Modified Files:
minion-spec.tex
Log Message:
Correct typos and omissions (thanks to PJM)
Index: minion-spec.tex
===================================================================
RCS file: /home/minion/cvsroot/doc/minion-spec.tex,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -d -r1.62 -r1.63
--- minion-spec.tex 16 Sep 2002 19:04:01 -0000 1.62
+++ minion-spec.tex 25 Sep 2002 15:25:08 -0000 1.63
@@ -7,39 +7,8 @@
1. Mail gateways. We should specify these.
[Should go into appendix]
-2. Need to write: algorithm for processing a reply.
-
- XXXX The thing is done, Nick please check it for bugs, and to find
- out if it is realistic. I still find it difficult to define the
- difference between forward path and SURBed messages since we do not
- have any special markers in the payload. -GD
-
- XXXX It looks okay; I'll triple-check it when I get there in the
- implementation (should be within the next week). I think that I
- may be coming around to your pt of view about encoding size and
- whatnot; maybe we should mark reply deliver too? (We need to
- figure out whether reply/junk indistinguishability really buys
- us anything. If not, we can put more stuff in reply tags. We
- probably need to anyway.) If we do this, we'll want to look at all
- uses of the 'TAG' field and maybe break it up a bit finder. -NM
-
-3. We should write the nymserver spec too. We can keep it pretty much
- separate from this Mixminion spec.
-
- I will start working on this as soon as I am back from Belgium (5
- Aug 02). I will try to put on paper the scribbles of the CFP
- napkins and additional issues. May be this is a better place to
- define general SMTP transport (except for last hop of SURB)
- instead of the general mixminion spec document. -GD
- Cool. -NM
-
4. Description of mixing algorithm should go in descriptor blocks. -NM
-5. We must change the crossover and message-generation algorithms to address
- George's attack of 15 August 2002.
-
- I've taken a rough cut at this, but I want George to check it out. -NM
-
6. We should specify: are 'DROP'-type messages dropped before they go
into the mix pool, or after they're pulled from the pool?
@@ -47,6 +16,10 @@
8. Specification for incoming SMTP interface.
+9. ``End-to-end'' issues (See Nick's mail of Sep2002)
+
+9. K-of-N delivery, compression, and fragments.
+
\section{FUTURE ISSUES}
(These are unresolved issues that we don't want to think about till we
@@ -274,9 +247,9 @@
// Calculate the Junk that will be appended during processing:
J_0 = ``'';
for i = 1 .. N
- J_i = J_(i-1) | PRNG(HASH(SK_i, ``RANDOM JUNK'')[0:16], SIZE_i)
+ J_i = J_(i-1) | PRNG(HASH(SK_i | ``RANDOM JUNK'')[0:16], SIZE_i)
- Stream_i = PRNG(HASH(SK_i, ``HEADER SECRET KEY''), 128*16);
+ Stream_i = PRNG(HASH(SK_i | ``HEADER SECRET KEY''), 128*16);
J_i = J_i XOR Stream_i[128*15 -Len(J_i) + SIZE_i:Len(J_i)];
end
@@ -290,7 +263,7 @@
EH = EXT( RI_i )
REST = Encrypt(K, (EH | H_(i+1)))
DIGEST = HASH(REST | J_i)
- H_i = ESHS(PK_i, V, SK_i, DIGEST, F, len(RI_i), RT_i, RI_i) | REST
+ H_i = ESHS(PK_i, V, SK_i, DIGEST, len(RI_i), RT_i, RI_i) | REST
end
return H_1;
@@ -324,19 +297,15 @@
Process:
// Phase 1
if (H2 is a reply block)
- P = SPRP_ENC(SURB secret key, P)
+ P = SPRP_ENC(SURB secret key, "PRIVATE SURB KEY", P)
else // (H2 is *not* a reply block)
for i = N .. 1
P = SPRP_ENC(SK2_i, "PAYLOAD ENCRYPT", P)
end
- else
+ endif
// Phase 2
H2 = SPRP_ENC(SHA1(P), ``HIDE HEADER'', H2)
-[XXXX We should add this to address George's attack of 15Aug. George,
- is this correct? Does it go here?
- XXXX This is correct -GD
P = SPRP_ENC(SHA1(H2), "HIDE PAYLOAD", P)
- - NM]
for i = N .. 1
H2 = SPRP_ENC(SK1_i, "HEADER ENCRYPT",H2)
@@ -367,11 +336,7 @@
if routing type is DROP:
End.
if routing type is SWAP-FWD:
-[XXXX We should add this to address George's attack of 15Aug. George,
- is this correct? Does it go here?
-[XXXX I think this is correct -GD]
P = SPRP_DEC(SHA1(H2), "HIDE PAYLOAD", P)
- -NM]
H2 = SPRP_DEC(SHA1(P), ``HIDE HEADER'', H2)
Swap H1 and H2;
if routing type is SWAP-FWD or FWD:
@@ -408,8 +373,7 @@
// We need here a convention for creating the
// Encryption key in the SURB.
- KEYX = HASH(seed| ``PRIVATE SURB KEY'')[0:16];
- M = SPRP_DEC(KEYX,M);
+ M = SPRP_DEC(seed, "PRIVATE SURB KEY",M);
P = M; exit;