1999-02-22 19:08:46 +00:00
|
|
|
List of some known bugs
|
|
|
|
|
-------------------------
|
|
|
|
|
|
|
|
|
|
This following list contains those bugs which we are aware of. Please
|
|
|
|
|
make sure that bugs you report are not listed here. If you can fix one
|
|
|
|
|
of these bugs/limitations we will certainly be glad to receive a patch.
|
|
|
|
|
(Please note that we need a disclaimer if a patch is longer than about
|
|
|
|
|
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.)
|
|
|
|
|
|
1999-03-05 12:56:11 +00:00
|
|
|
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.
|
1999-02-22 19:08:46 +00:00
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
|
|
|
|
|
[ *] #1
|
|
|
|
|
pgp263in works fine even with a source file with CR,LF but GnuPG
|
|
|
|
|
and pgp263in has problems if the clearsign has been created by
|
1999-05-19 14:12:26 +00:00
|
|
|
pgp263ia. The reason for this problem is that pgp2 sometimes
|
|
|
|
|
converts CR,LF to CR,CR,LF and to fix for this it hashes both
|
|
|
|
|
versions. I was able to reproduce such a problem, that PGP263in
|
|
|
|
|
was not able to verify it's own signature.
|
|
|
|
|
FIX: 1999-05-19 (Most cases are now handled)
|
1999-02-22 19:08:46 +00:00
|
|
|
|
|
|
|
|
[ *] #3
|
|
|
|
|
--list-packets should continue even w/o a passphrase (or in batch
|
|
|
|
|
mode). Maybe we have to move it to a separate program??
|
|
|
|
|
|
|
|
|
|
[ *] #4 1999-01-13 <ralf.stephan@fitug.de> 0.9.1
|
|
|
|
|
v3 key 'expiration date' problem:
|
|
|
|
|
1. generate a key, set expiration date
|
|
|
|
|
2. <do other things, deleting etc.>
|
|
|
|
|
3. edit a v3 secret key, try to set expiration date
|
|
|
|
|
- output: "You can't change...
|
|
|
|
|
4. save
|
|
|
|
|
5. key has expiration date from 1. and gpg reports that pubkey
|
|
|
|
|
and seckey differ.
|
|
|
|
|
The for loop the exp.date is set before v3 detection?
|
1999-05-06 12:26:10 +00:00
|
|
|
[is this bug still alive?]
|
1999-02-22 19:08:46 +00:00
|
|
|
|
|
|
|
|
[ *] #5
|
|
|
|
|
/home/jam/.gnupg/pubring.gpg: can't open gdbm file: Can't be writer
|
|
|
|
|
keyblock resource `/home/jam/.gnupg/pubring.gpg': file open error
|
|
|
|
|
OOPS in close enum_keyblocks - ignored
|
|
|
|
|
[gdbm is experimental and will be replaced by the new keybox code]
|
|
|
|
|
|
1999-02-22 20:07:08 +00:00
|
|
|
[***] #6 1999-02-22 <backes@rhrk.uni-kl.de> 0.9.3
|
|
|
|
|
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.
|
1999-03-14 18:35:18 +00:00
|
|
|
--> Solaris fixed.
|
|
|
|
|
--> IRIX bug still there
|
1999-02-22 20:07:08 +00:00
|
|
|
|
1999-03-10 10:27:52 +00:00
|
|
|
|
1999-05-19 14:12:26 +00:00
|
|
|
[ **] #17 1999-05-18 <Bodo_Moeller@public.uni-hamburg.de> 0.9.6
|
|
|
|
|
Import does not detect identical user IDs.
|
1999-05-22 20:54:54 +00:00
|
|
|
FIX: 1999-05-22
|
1999-05-19 14:12:26 +00:00
|
|
|
|
|
|
|
|
Next #18
|
1999-03-10 10:27:52 +00:00
|
|
|
|
