1
0
mirror of git://git.gnupg.org/gnupg.git synced 2024-12-22 10:19:57 +01:00
gnupg/TODO

38 lines
1.6 KiB
Plaintext
Raw Normal View History

1997-11-21 14:53:57 +00:00
1997-11-27 11:44:13 +00:00
* add assembler support for more CPUs. (work, but easy)
1997-11-21 14:53:57 +00:00
* improve iobuf by reading more than one byte at once,
this shoud espceially done for the buffer in the chain.
* add a way to difference between errors and eof in the underflow/flush
function of iobuf.
1997-12-09 12:46:23 +00:00
* check that all output is filtered when displayed.
1997-11-21 14:53:57 +00:00
* add trust stuff
* add checking of armor trailers
* add real secure memory
* look for a way to reuse RSA signatures
* remove all "Fixmes"
* speed up the RIPE-MD-160
1997-11-24 11:04:11 +00:00
* add signal handling
1997-11-23 15:38:27 +00:00
* enable a SIGSEGV handler while using zlib functions
1997-11-21 14:53:57 +00:00
1997-12-02 19:36:53 +00:00
* PGP writes the signature and then the file, this is not
1997-12-09 12:46:23 +00:00
a good idea, we can't write such files if we take input from stdin.
1997-12-02 19:36:53 +00:00
So the solution will: accept such packet, but write
signature the corret way: first the data and then the signature[s]
this is much easier to check, also we must read the entire data
before we can check wether we have the pubkey or not. The one-pass
signature packets should be implemented to avoid this.
1997-12-12 12:03:58 +00:00
* complete cipher/cast.c
* complete cipher/dsa.c
1997-12-09 12:46:23 +00:00
1997-12-16 19:15:09 +00:00
* define a standard way to specify keyid/userid and other stuff
to identify a user. We could look at the first character and
say: If it's a digit, a keyid follows (need to add a zero in
case the keyid starts with A..F); if it is a left angle bracket,
this is a email address and should be used, all others are substrings
of the userid.
[can be handles in get_pubkey_by_name()]
1998-01-02 20:40:10 +00:00
* armor has now some problems.