[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[minion-cvs] Refer to A.3 in 4, in case people dont read the whole t...
Update of /home/minion/cvsroot/doc/spec
In directory moria:/tmp/cvs-serv13946/doc/spec
Modified Files:
minion-spec.txt
Log Message:
Refer to A.3 in 4, in case people dont read the whole thing.. Also: Mixminion, not MixMinion.
Index: minion-spec.txt
===================================================================
RCS file: /home/minion/cvsroot/doc/spec/minion-spec.txt,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -d -r1.29 -r1.30
--- minion-spec.txt 27 Jul 2004 07:48:53 -0000 1.29
+++ minion-spec.txt 2 Dec 2005 19:04:06 -0000 1.30
@@ -1040,18 +1040,21 @@
must initiate key renegotiation. If it has not, the server must
close the connection.
- NOTE:
+ NOTES:
The old keys must be permanently overwritten. Special care should be
taken to permanently erase them from the Hard Disk and memory.
- The standard transport mechanism over which the MixMinion Transfer
+ The standard transport mechanism over which the Mixminion Transfer
Protocol talks is TCP over IP. The standard listening TCP port should be
number 48099 (until we register a port with www.iana.org)
- All possible checks should be performed during the transfer protocol
- and if any fail the connection MUST stop and all state MUST
- be deleted. An error MAY be logged.
+ All possible checks should be performed during the transfer protocol and
+ if any fail the connection MUST stop and all state MUST be deleted. An
+ error MAY be logged.
+
+ Current implementations do not report their version as 1.0. See appendix
+ A.3.
A.1. Appendix: A suggested pooling rule