/[pkg-mixmaster]/trunk/Mix/TODO
ViewVC logotype

Contents of /trunk/Mix/TODO

Parent Directory Parent Directory | Revision Log Revision Log


Revision 161 - (show annotations) (download)
Wed Aug 21 18:00:01 2002 UTC (10 years, 10 months ago) by rabbi
File size: 1564 byte(s)
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.
1 Mandatory todo items before 3.0 release:
2
3 * autoconf installation script is needed
4 * post-install scripts need to be reworked
5 * provide a packaged Windows build to be used with QuickSilver
6 * clean up documentation and tarball contents
7 * do full regression tests on as many platforms possible
8 + list only these platforms as supported
9 * resolve any new critical issues
10
11 Items for 3.0 or 3.0.1
12
13 * allow for verification of clearsigned OpenPGP messages
14 * AES support -- requires OpenSSL 0.9.7
15 * further mpgp testing of AES/MDC packet support
16 * honor key preferences when encrypting to multiple keys
17 * Macintosh OS/X support
18 * Windows build instructions/files
19 * documentation issues resolved
20 + mpgp man page
21 * check and enforce OpenPGP key expiration date
22 * Implement mbox/Maildir mail input (597043)
23 * Have supported cpunks/mixes in -conf reply
24 similar to Reliable (480330)
25 * further debugging
26
27 Further wishlist:
28
29 * set an expiration date on OpenPGP keys
30 * Allow sending with middlemen remailers last
31 in chain in interactive mixmaster (481244)
32 * investigate whether and how it is feasible to
33 add expiration/creation dates to mixmaster keys
34 if feasible, implement setting and checking
35 * Add FOOTER setting (490117)
36 * Automatic key handling:
37 + create new PGP keys automatically if
38 current keys are about to expire
39 + requires implementing key signing, key deletion
40 + create new mixmaster keys automatically
41 if necessary
42 + Automatically announce new keys?
43 - implement remailer-key signing?
44 - if yes, which key?
45 * make mpgp friendlier

  ViewVC Help
Powered by ViewVC 1.1.5