aboutsummaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
Diffstat (limited to 'TODO')
-rw-r--r--TODO23
1 files changed, 10 insertions, 13 deletions
diff --git a/TODO b/TODO
index 66a1c43c3..5108cfee5 100644
--- a/TODO
+++ b/TODO
@@ -1,5 +1,5 @@
- * 12345678! does not work anymore
+ * 12345678! does not work anymore. Same for +wordlist.
* Always use the primary key to sign other keys.
@@ -64,10 +64,6 @@
* Replace the printing of the user name by [self-signature] when
appropriate so that a key listing does not get clobbered.
- * "Michael T. Babcock" <[email protected]> suggested to write
- an event log so that other software can display a key history or
- alike with GnuPG results. This should be connected to the keyrings.
-
* Using --list-only to check for recipients while decrypting may
yield an error about an unknown packet.
@@ -82,6 +78,11 @@
* Allow to update key signatures.
+ * For FreeBSD only: spit out a message that rndcontrol (8) should be
+ used to enable the use of IRQs for entropy gathering.
+
+ * --passphrase-fd can't work with -cs: document this or find a way
+ to work around.
Scheduled for 1.1
-----------------
@@ -91,8 +92,6 @@ Scheduled for 1.1
* With option -i prompt before adding a key to the keyring and show some
info what we are about to add.
- * Speed up calculation of key validation.
-
* --disable-asm should still assemble _udiv_qrnnd when needed
* Skip RO keyrings when importing a key.
@@ -105,6 +104,9 @@ Scheduled for 1.1
* Get new assembler stuff from gmp 3.1
+ * Use new-format headers for compressed packets.
+
+
Nice to have
------------
@@ -113,9 +115,6 @@ Nice to have
* Print a warning if the directory mode is wrong.
* Do a real fix for bug #7 or document that it is a PGP 5 error.
* preferences of hash algorithms are not yet used.
- * Replace the SIGUSR1 stuff by semaphores to avoid loss of a signal.
- or use POSIX.4 realtime signals. Overhaul the interface and the
- test program. Use it with the test suite?
* add test cases for invalid data (scrambled armor or other random data)
* add checking of armor trailers
* the pubkey encrypt functions should do some sanity checks.
@@ -124,8 +123,6 @@ Nice to have
* for messages created with "-t", it might make sense to append the
verification status of the message to the output (i.e. write something to
the --output file and not only to stderr.
- * configure option where to find zlib
- * Evaluate whether it make sense to replace the namehashs either by
- using the user ID directly or by using pointers into the trustdb.
+