1 2 * Change the internal representation of keyid into a struct which 3 can also hold the localid and extend the localid to hold information 4 of the subkey number because two subkeys may have the same keyid. 5 6 * Add a way to override the current cipher/md implementations 7 by others (using extensions) 8 9 * Not GnuPG related: What about option completion in bash? 10 Can "--dump-options" be used for this or should we place the 11 options in an ELF note section? 12 13 * Split key support (n-out-of-m). Use our own protocol or figure out 14 how PGP does it. 15 16 * add an option to re-create a public key from a secret key; we 17 can do this in trustdb.c:verify_own_keys. (special tool?) 18 Hmmm, we better drop the duplication of the public part and just keep 19 the secrets in the "secring" - this has the additional that we can 20 put those secrets on a hardware token. 21 22 * write a tool to extract selected keys from a file. 23 24 * Change the buffering to a mbuf like scheme? See Michael's proposal. 25 26 * Keep a list of duplicate, faked or unwanted keyids. 27 28 * The current code has knowledge about the structure of a keyblock. 29 We should add an abstraction layer so that adding support for 30 different certificate structures will become easier. 31 32 * "Michael T. Babcock" <mbabcock@fibrespeed.net> suggested to write 33 an event log so that other software can display a key history or 34 alike with GnuPG results. This should be connected to the keyrings. 35 36 37 38 Copyright 1998, 1999, 2000, 2001 Free Software Foundation, Inc. 39 40 This file is free software; as a special exception the author gives 41 unlimited permission to copy and/or distribute it, with or without 42 modifications, as long as this notice is preserved. 43 44 This file is distributed in the hope that it will be useful, but 45 WITHOUT ANY WARRANTY, to the extent permitted by law; without even the 46 implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. 47