summaryrefslogtreecommitdiffstats
path: root/BUGS
diff options
context:
space:
mode:
authorWerner Koch <wk@gnupg.org>1999-02-26 17:59:48 +0100
committerWerner Koch <wk@gnupg.org>1999-02-26 17:59:48 +0100
commit694099b9af96d53ad4a4f9bc70e08c2f393f9f4e (patch)
treeff5ddc557b85093cbf4076374bd43b2e958ce804 /BUGS
parentSee ChangeLog: Thu Feb 25 18:47:39 CET 1999 Werner Koch (diff)
downloadgnupg2-694099b9af96d53ad4a4f9bc70e08c2f393f9f4e.tar.xz
gnupg2-694099b9af96d53ad4a4f9bc70e08c2f393f9f4e.zip
See ChangeLog: Fri Feb 26 17:55:41 CET 1999 Werner Koch
Diffstat (limited to 'BUGS')
-rw-r--r--BUGS18
1 files changed, 8 insertions, 10 deletions
diff --git a/BUGS b/BUGS
index da991bd08..8f98aa586 100644
--- a/BUGS
+++ b/BUGS
@@ -42,29 +42,27 @@ an "info standards" to find out why a disclaimer is needed for GNU.)
Buserror on IRIX 6.4: Crash while doing a keygen. I think while creating
the prime. Other buserrors are reported when doing a "gpg README"
on sparc-solaris2.6.
- --> I hope I've fixed this: Please, can someone it. I can't reproduce it
- on the alpha I have access to.
+ --> I hope I've fixed this: Please, can check someone it.
+ I can't reproduce it on the alpha I have access to.
-[ **] #7 1999-02-22 <dwpalmer@dwpalm.jf.intel.com> 0.9.3
+[ *] #7 1999-02-22 <dwpalmer@dwpalm.jf.intel.com> 0.9.3
Conventional encrytion incompatibilty:
$ gpg -c --cipher-algo cast5 --compress-algo 1 --no-comment secrets.txt
Creates a file that gpg can decrypt, but PGP 5.5 has problems with it.
PGP decrypts 6416k out of 6424k, then complains with "PGP Warning",
"The keyring contains a bad (corrupted) PGP packet". The resulting
file is missing information from the front.
+ [26.02.99: temporary fix in encrypt_simple()
-[ *] #8 1999-02-25 <kazu@iijlab.net>
+[ ] #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
- because GNUPG encrypted a message with a random session key first then
- tries to find public keys specified with the -r option. I don't like
- this.
+ [26.02.99 fixed]
-[ **] #9 1999-02-25
+[ ] #9 1999-02-25
Misalignment in md5.c#md5_write.
-
+ [26.02.99 fixed]