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

Contents of /trunk/Mix/TODO

Parent Directory Parent Directory | Revision Log Revision Log


Revision 214 - (show annotations) (download)
Thu Sep 5 01:21:54 2002 UTC (10 years, 8 months ago) by weaselp
File size: 2045 byte(s)
Mixmaster keys now have creation and expiration date.
It is not secured by any crypto voodoo, it's only
informational for clients to decide which keys to
use should they have more.
- on the client side we do not show remailers (and
  therefore not use them) if their key is expired.
- the remailer refuses to decrypt messages to keys
  that expired one month ago or earlier.
- the remailer automatically creates new mixmaster
  keys if the current one are about to expire or
  already are expired.
- the latest key from secring.mix is written to
  key.txt. It used to be the first one. Since
  creation of new mix key appends the key, this
  seemed sensible.
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 * keylifetime and key{grace,overlap}period needs to be documented once
11 it's finished; seems to work nicely for mixmaster keys so far, pgp
12 still giving problems
13 - move self/binding signatures to the secret keyrings
14 - display expiration date in ascii summary of keys
15 - if there is no expiration date on existing keys,
16 do _not_ add one, if there already is an expiration
17 date on they key, do _not_ change it
18 - only list the latest key of each type in pgpkeys.txt
19 (similar to how weasel's patch does it with mix keys)
20 - make keymgt(0|1) create new pgp keys if old ones are
21 expires/due to expire
22 - for later: do not encrypt to expired keys, do not
23 decrypt to keys that expired longer than graceperiod ago
24
25 Items for 3.0 or 3.0.1
26
27 * create internally-generated dummy messages
28 * support a list of remailers not to be selected as *.
29 * allow for verification of clearsigned OpenPGP messages
30 * AES support -- requires OpenSSL 0.9.7
31 * further mpgp testing of AES/MDC packet support
32 * honor key preferences when encrypting to multiple keys
33 * Macintosh OS/X support
34 * Windows build instructions/files
35 * documentation issues resolved
36 + mpgp man page
37 * check and enforce OpenPGP key expiration date
38 * further debugging
39
40 Further wishlist:
41
42 * Automatic key handling:
43 + create new PGP keys automatically if
44 current keys are about to expire
45 + requires implementing key signing, key deletion
46 + create new mixmaster keys automatically
47 if necessary (almost done, see keylifetime etc above)
48 + Automatically announce new keys?
49 - implement remailer-key signing?
50 - if yes, which key?
51 * make mpgp friendlier
52 * store nym public keys locally

  ViewVC Help
Powered by ViewVC 1.1.5