Parent Directory
| 
Revision Log
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?
| 1 | rabbi | 127 | Todo items before 3.0 release: |
| 2 | rabbi | 1 | |
| 3 | rabbi | 127 | * autoconf installation script is needed |
| 4 | * post-install scripts need to be reworked | ||
| 5 | * Macintosh OS/X support | ||
| 6 | * further mpgp testing of AES/MDC packet support | ||
| 7 | rabbi | 152 | * honor key preferences when encrypting to multiple keys |
| 8 | rabbi | 127 | * Windows build instructions/files |
| 9 | * documentation issues resolved | ||
| 10 | rabbi | 141 | + mpgp man page |
| 11 | * allow for verification of clearsigned OpenPGP messages | ||
| 12 | weaselp | 140 | * set an expiration date on OpenPGP keys |
| 13 | * check and enforce expiration date | ||
| 14 | * Implement mbox/Maildir mail input (597043) | ||
| 15 | weaselp | 142 | * further debugging |
| 16 | weaselp | 140 | |
| 17 | Further wishlist: | ||
| 18 | * Allow sending with middlemen remailers last | ||
| 19 | in chain in interactive mixmaster (481244) | ||
| 20 | * Have supported cpunks/mixes in -conf reply | ||
| 21 | (480330) | ||
| 22 | * investigate whether and how it is feasible to | ||
| 23 | add expiration/creation dates to mixmaster keys | ||
| 24 | if feasible, implement setting and checking | ||
| 25 | * Add FOOTER setting (490117) | ||
| 26 | * Automatic key handling: | ||
| 27 | + create new PGP keys automatically if | ||
| 28 | current keys are about to expire | ||
| 29 | + requires implementing key signing, key deletion | ||
| 30 | + create new mixmaster keys automatically | ||
| 31 | if necessary | ||
| 32 | + Automatically announce new keys? | ||
| 33 | - implement remailer-key signing? | ||
| 34 | - if yes, which key? | ||
| 35 | rabbi | 141 | * make mpgp friendlier |
| ViewVC Help | |
| Powered by ViewVC 1.1.5 |