Log of /trunk/Mix/TODO
Parent Directory
| 
Revision Log
Revision
171 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Thu Aug 22 08:13:36 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 1322 byte(s)
Diff to
previous 167
Also list cypherpunk remailers in remailer-conf reply. Thanks to Ulf and
Disastry for their help.
Revision
165 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Thu Aug 22 04:01:16 2002 UTC
(10 years, 9 months ago)
by
weaselp
File length: 1428 byte(s)
Diff to
previous 164
When sending type II messages interactivly you may now choose a middleman
remailer as the last hop in your chain (closes: #481244).
Revision
161 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Wed Aug 21 18:00:01 2002 UTC
(10 years, 9 months ago)
by
rabbi
File length: 1564 byte(s)
Diff to
previous 152
Re-introduced the todo list with Reality.
Basically, if the install process is made friendly and saner, and we've
done real testing on the major platforms, I'm not too interested in holding
up 3.0 any longer. Everything else can be done in the point release.
Should we:
* leave AES support #ifdef'd out if OpenSSL 0.9.7 isn't released?
* support AES if the installed version of OpenSSL is 0.9.7beta3 or greater?
* include the necessary AES source from OpenSSL, as per the original patch?
I'm leaning toward option two, though we should still display the "this
version of OpenSSL is untested" message for 0.9.7. FWIW, 0.9.7beta3 has been
working fine for me on randseed.
Revision
152 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Modified
Wed Aug 21 07:03:37 2002 UTC
(10 years, 9 months ago)
by
rabbi
File length: 1213 byte(s)
Diff to
previous 150
Currently, if Mixmaster is encrypting mail to multiple recipients, it does
not honor key preferences, and defaults to 3DES with no MDC.
It should choose the "most prefered" settings between the recipients, only
using 3DES/MDC if no other choice is available.
(We'll have to make some reasonable tie-breaking decisions, too -- for
instance, if one key lists AES,CAST and another lists CAST,AES -- which do
we take? I think we should have an internal "preference order" that is
used in these cases. I propose AES128,AES256,AES192,CAST5,3DES,IDEA,BLOW).
We'll want to use the MDC feature in all possible cases. Fixing this is
most important -- I'd be okay with using 3DES whenever we have multiple
recipients, as long as we could use MDC if they each advertised either
support for it in the features flag, or support for ciphers 7,8,9, or 10
(even though we don't support 10).
Hmm. Something else to check -- PGP 7.x can decrypt MDC when used with
3DES, right?
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
enter a numeric revision.
