aboutsummaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>1998-11-20 19:22:58 +0000
committerWerner Koch <[email protected]>1998-11-20 19:22:58 +0000
commit710d2e351bfd9f97f7a45359d269e7620865cfb7 (patch)
treec5272c8c44ec561672ef8960d8a51e6068fdc568 /TODO
parentExpiration time works (I hope so) (diff)
downloadgnupg-0-4-4.tar.gz
gnupg-0-4-4.zip
Ready for version 0.4.4V0-4-4
Diffstat (limited to '')
-rw-r--r--TODO18
1 files changed, 8 insertions, 10 deletions
diff --git a/TODO b/TODO
index 8e80e2d87..276582a80 100644
--- a/TODO
+++ b/TODO
@@ -1,5 +1,11 @@
- * hash calculation for cleartext sigs without a "Hash: xxx" line
+ * Check revocation and expire stuff.
+
+ * Check calculation of key validity.
+
+ * preferences of hash algorithms are not yet used.
+
+ * Hash calculation for cleartext sigs without a "Hash: xxx" line
does it work as specified in the RFC? - Hmmm, I think so
* Check Berkeley BD - it is in glibc -any licensing problems?
@@ -10,9 +16,7 @@
* Update the keyring at ftp.guug.de
- * expire date is not shown in --edit-key for subkeys.
-
- * check support for mpi/powerpc
+ * check support for mpi/powerpc (see Brian's mail)
* use zlib 1.1.13 to avoid a bug with 13 bit windows
but there are more problems with large files
@@ -26,8 +30,6 @@
* clearsig: keep lineendings as they are. Remember that trailings
blanks are not hashed.
- * Check revocation and expire stuff.
-
* Always use the latest key signature (import). This is needed, so
that we are able to chnage the expiration time or other info in the
selfsignature
@@ -49,8 +51,6 @@
* new menu to delete signatures and list signature in menu
- * commandline controlled --edit-key with assumed save.
-
* -rdynamic auf Solaris Problem
* Replace the SIGUSR1 stuff by semaphores to avoid loss of a signal.
@@ -60,8 +60,6 @@
* add some sanity checks to read_keyblock, so that we are sure that
the minimal requirements are met (?)
- * preferences of hash algorithms are not yet used.
-
* rewrite --list-packets or put it into another tool.
* Burn the buffers used by fopen(), or use read(2). Does this