diff options
| author | Werner Koch <wk@gnupg.org> | 1999-03-05 13:56:11 +0100 |
|---|---|---|
| committer | Werner Koch <wk@gnupg.org> | 1999-03-05 13:56:11 +0100 |
| commit | 12b5d34ad39fe464470511842e50bbddbc24aeef (patch) | |
| tree | 7abe9ce5e3781930a3b159f65b3e89071636ddf6 /BUGS | |
| parent | See ChangeLog: Tue Mar 2 16:44:57 CET 1999 Werner Koch (diff) | |
| download | gnupg2-12b5d34ad39fe464470511842e50bbddbc24aeef.tar.xz gnupg2-12b5d34ad39fe464470511842e50bbddbc24aeef.zip | |
*** empty log message ***
Diffstat (limited to 'BUGS')
| -rw-r--r-- | BUGS | 28 |
1 files changed, 27 insertions, 1 deletions
@@ -8,7 +8,9 @@ of these bugs/limitations we will certainly be glad to receive a patch. 10 lines; but it may help anyway to show us where we have to fix it. Do an "info standards" to find out why a disclaimer is needed for GNU.) -(format: severity: [ *] to [***], no, first reported, by, version) +Format: severity: [ *] to [***], no, first reported, by, version. +Bugs which are marked with "FIX: yyyy-mm-dd" are fixed in the CVS +and after about half a day in the rsync snapshots. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ *] #1 @@ -16,6 +18,12 @@ an "info standards" to find out why a disclaimer is needed for GNU.) and pgp263in has problems if the clearsign has been created by pgp263ia. +[***] #2 1999-02-21 + Problem while importing or deleting public keys in 0.9.3 - 0.9.2 + worked fine. Error message: + gpg:[stdin]: key A6A59DB9: secret key not found: public key not found + FIX: 1999-02-22 wk + [ *] #3 --list-packets should continue even w/o a passphrase (or in batch mode). Maybe we have to move it to a separate program?? @@ -54,5 +62,23 @@ an "info standards" to find out why a disclaimer is needed for GNU.) file is missing information from the front. [26.02.99: temporary fix in encrypt_simple()] +[ *] #8 1999-02-25 <kazu@iijlab.net> 0.9.3 + %gpg --encrypt -r kazu@iijlab.net --batch foo + gpg: Warning: using insecure memory! + gpg: 11C23F61: no info to calculate a trust probability + This creates a symmetrically encrypted message WITHOUT a session key + encrypted with public cryptographic(i.e. foo.gpg). This is probably + FIX: 199-02-26 wk + +[ **] #9 1999-02-25 + Misalignment in md5.c#md5_write. + FIX: 1999-02-26 wk + +[ **] #10 1999-03-01 + Armor detection code is broken. Direct import of keyrings is not possible. + FIX: 1999-03-02 wk +[***] #11 1999-02-25 + "cipher algo 10 not found". + FIX: 1999-02-25 wk |