summaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>1999-05-08 19:35:16 +0200
committerWerner Koch <wk@gnupg.org>1999-05-08 19:35:16 +0200
commita1dcec76c1f85b95c1eff73d12c1c13f699aaecb (patch)
treea041bdf1210b06678f548af47f1ab65fe23ca973 /TODO
parent. (diff)
downloadgnupg2-a1dcec76c1f85b95c1eff73d12c1c13f699aaecb.tar.xz
gnupg2-a1dcec76c1f85b95c1eff73d12c1c13f699aaecb.zip
See ChangeLog: Sat May 8 19:28:33 CEST 1999 Werner Koch
Diffstat (limited to 'TODO')
-rw-r--r--TODO6
1 files changed, 4 insertions, 2 deletions
diff --git a/TODO b/TODO
index 250c10d11..c835bae73 100644
--- a/TODO
+++ b/TODO
@@ -28,8 +28,10 @@
Nice to have
------------
+ * Let take --help an option to select some topics.
* Offcial test vectors for 3DES-EDE3
* use DEL and ^H for erasing the previous character (util/ttyio.c).
+ or better readline.
* Print a warning if the directory mode is wrong.
* replace the keyserver stuff either by a call to a specialized
utility or SOCKSify the stuff.
@@ -43,8 +45,8 @@ Nice to have
* add test cases for invalid data (scrambled armor or other random data)
* add checking of armor trailers
* Burn the buffers used by fopen(), or use read(2). Does this
- really make sense?
- * change the fake_data stuff to mpi_set_opaque
+ really make sense? And while we are at it: implement a secure deletion
+ stuff?
* Stats about used random numbers.
* the pubkey encrypt functions should do some sanity checks.
* dynload: implement the hint stuff.