diff options
author | Werner Koch <wk@gnupg.org> | 1999-09-01 15:40:07 +0200 |
---|---|---|
committer | Werner Koch <wk@gnupg.org> | 1999-09-01 15:40:07 +0200 |
commit | 0428ca6da6d18a2579fe81a1a77e184007bab9fb (patch) | |
tree | 644594a4ddc9d68649ecad3df72f5e97f5832588 /PROJECTS | |
parent | See ChangeLog: Tue Aug 31 17:20:44 CEST 1999 Werner Koch (diff) | |
download | gnupg2-0428ca6da6d18a2579fe81a1a77e184007bab9fb.tar.xz gnupg2-0428ca6da6d18a2579fe81a1a77e184007bab9fb.zip |
See ChangeLog: Wed Sep 1 15:30:44 CEST 1999 Werner Koch
Diffstat (limited to 'PROJECTS')
-rw-r--r-- | PROJECTS | 31 |
1 files changed, 5 insertions, 26 deletions
@@ -1,47 +1,26 @@ - * Check if an object (a message, detached sign, public key, or whatever) - is signed by definite user, i.e. define user - (userid, or any other unique identification) on command line. - --> NO: Use a script and --status-fd - * Change the internal representation of keyid into a struct which can also hold the localid and extend the localid to hold information of the subkey number because two subkeys may have the same keyid. - * signature verification is done duplicated on import: in import.c and - then in trustdb.c too. Maybe we can use a flag to skip the actual - verification process (this should work if we use the same keyblock, - but I'm not sure how to accomplish that). Another way is to allow - the import of bogus data and let trustdb mark these keys as invalid; - I see an advantage in this that it may help to prevent a DoS on a - keyserver by sending him a lot of bogus signatures which he has - to check - Needs further investigation. - * Add a way to override the current cipher/md implementations by others (using extensions) * Not GnuPG related: What about option completion in bash? Can "--dump-options" be used for this or should we place the - options in a special ELF segment? + options in an ELF note section? - * Split key support (n-out-of-m) + * Split key support (n-out-of-m). Use our own protocol or figure out + how PGP does it. * add an option to re-create a public key from a secret key; we - can do this in trustdb.c:verify_own_keys. - (special tool?) + can do this in trustdb.c:verify_own_keys. (special tool?) * rewrite --list-packets or put it into another tool. - * We need a maintenance pass over the trustdb which flags - signatures as expired if the key used to make the signature has - expired. Maybe it is a good idea to store the expiration time - in the key record of the trustdb. * write a tool to extract selected keys from a file. - * Change the buffering to a mbuf like scheme? Need it for PSST anyway; - see Michael's proposal. - - * Work on the library + * Change the buffering to a mbuf like scheme? See Michael's proposal. * Keep a list of duplicate, faked or unwanted keyids. |