head	1.33;
access;
symbols
	V1-1-2:1.33
	V1-0-4:1.28.2.1
	V1-0-3:1.28.2.1
	V1-0-2:1.28.2.1
	ePit-1-0:1.28.2.1.0.2
	V1-0-1-ePit-1:1.28.2.1
	V1-0-1:1.28.2.1
	V1-1-0:1.29
	STABLE-BRANCH-1-0:1.28.0.2
	DEVEL-BRANCH-1-1:1.28
	V1-0-0:1.27
	V0-9-11:1.26
	V0-9-10:1.25
	V0-9-9:1.25
	V0-9-8:1.22
	V0-9-7:1.18
	V0-9-6:1.15
	V0-9-5:1.12
	V0-9-4:1.9;
locks; strict;
comment	@# @;


1.33
date	2000.01.24.11.55.41;	author wkoch;	state Exp;
branches;
next	1.32;

1.32
date	99.12.31.11.44.24;	author wkoch;	state Exp;
branches;
next	1.31;

1.31
date	99.12.08.21.02.53;	author wkoch;	state Exp;
branches;
next	1.30;

1.30
date	99.11.13.16.43.05;	author wkoch;	state Exp;
branches;
next	1.29;

1.29
date	99.10.26.12.14.04;	author wkoch;	state Exp;
branches;
next	1.28;

1.28
date	99.09.13.08.56.38;	author wkoch;	state Exp;
branches
	1.28.2.1;
next	1.27;

1.27
date	99.09.06.18.10.08;	author wkoch;	state Exp;
branches;
next	1.26;

1.26
date	99.08.31.15.30.01;	author wkoch;	state Exp;
branches;
next	1.25;

1.25
date	99.07.23.12.02.46;	author wkoch;	state Exp;
branches;
next	1.24;

1.24
date	99.07.22.18.11.47;	author wkoch;	state Exp;
branches;
next	1.23;

1.23
date	99.07.12.16.49.09;	author wkoch;	state Exp;
branches;
next	1.22;

1.22
date	99.06.26.10.22.46;	author wkoch;	state Exp;
branches;
next	1.21;

1.21
date	99.06.16.18.25.33;	author wkoch;	state Exp;
branches;
next	1.20;

1.20
date	99.06.15.12.30.55;	author wkoch;	state Exp;
branches;
next	1.19;

1.19
date	99.05.31.17.49.22;	author wkoch;	state Exp;
branches;
next	1.18;

1.18
date	99.05.23.18.32.26;	author wkoch;	state Exp;
branches;
next	1.17;

1.17
date	99.05.22.20.54.41;	author wkoch;	state Exp;
branches;
next	1.16;

1.16
date	99.05.19.14.12.20;	author wkoch;	state Exp;
branches;
next	1.15;

1.15
date	99.05.06.12.25.57;	author wkoch;	state Exp;
branches;
next	1.14;

1.14
date	99.04.06.18.04.48;	author wkoch;	state Exp;
branches;
next	1.13;

1.13
date	99.04.05.20.11.49;	author wkoch;	state Exp;
branches;
next	1.12;

1.12
date	99.03.20.11.56.56;	author wkoch;	state Exp;
branches;
next	1.11;

1.11
date	99.03.14.18.35.13;	author koch;	state Exp;
branches;
next	1.10;

1.10
date	99.03.10.10.27.47;	author koch;	state Exp;
branches;
next	1.9;

1.9
date	99.03.08.19.50.01;	author koch;	state Exp;
branches;
next	1.8;

1.8
date	99.03.05.12.56.11;	author koch;	state Exp;
branches;
next	1.7;

1.7
date	99.03.02.09.41.45;	author koch;	state Exp;
branches;
next	1.6;

1.6
date	99.02.26.16.59.38;	author koch;	state Exp;
branches;
next	1.5;

1.5
date	99.02.25.17.51.50;	author koch;	state Exp;
branches;
next	1.4;

1.4
date	99.02.25.12.03.29;	author koch;	state Exp;
branches;
next	1.3;

1.3
date	99.02.24.10.12.20;	author koch;	state Exp;
branches;
next	1.2;

1.2
date	99.02.22.20.07.08;	author koch;	state Exp;
branches;
next	1.1;

1.1
date	99.02.22.19.08.40;	author koch;	state Exp;
branches;
next	;

1.28.2.1
date	99.11.22.10.10.15;	author wkoch;	state Exp;
branches;
next	;


desc
@@


1.33
log
@See ChangeLog: Mon Jan 24 13:04:28 CET 2000  Werner Koch
@
text
@		   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.)

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.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

[  *] #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?
    [is this bug still alive? - can someone please check it]

[ **] #6 1999-02-22 <backes@@rhrk.uni-kl.de> 0.9.3
    Bus error on IRIX 6.4: Crash while doing a keygen. I think while creating
    the prime.	Other bus errors are reported when doing a "gpg README"
    on sparc-solaris2.6.
    --> Solaris fixed.
    --> IRIX bug still there but someone should test this again!
	(<mack@@sgi.com> reports that it is still alive in 1.0.0)
	(seems to be fixed now. wk 2000-01-14)

[  *] #18 1999-05-27 <Steffen.Zahn@@icn.siemens.de> 0.9.7
    rndunix hangs on hp/ux.  The problem is related to my_plcose which is
    not always called.	(I suggest to use EGD instead of rndunix.)


[  *] #24 1999-09-05 <marcus@@yoyo.cc.monash.edu.au> 0.9.11
    Does not link libc and libz expect when removing all "-lc -lz" except
    for the last one.  This happens on some systems when not using the
    GNU ld.  This need to be fixed in libtool.

[  *] #28 1999-11-29
    --list-key will only emit an error about unknown UIDs when all UIDs
    are unknown.
    [Postponed for 1.2]

[  *] #30 1999-12-16 <pfeifer@@dbai.tuwien.ac.at>
    Using -r with a name does not check for multiple recpients and may
    lead to unwanted recipients.

[  *] #31 199-12-24 Jeff Allen <jra@@corp.webtv.net>
    VPATH build in a subdirectory of the sources does not work for po files.

Next #31
@


1.32
log
@See ChangeLog: Fri Dec 31 12:48:31 CET 1999  Werner Koch
@
text
@d39 1
@


1.31
log
@See ChangeLog: Wed Dec  8 21:58:32 CET 1999  Werner Koch
@
text
@a43 9
[  *] #22 1999-07-22
    Solaris make has problems with the generated POTFILES - seems to be a
    gettext bug.  Use GNU make as a workaround.
    FIX: 1999-12-03 (meanwhile fixed in gettext)

[  *] #23 1999-09-03 <todd.brooks@@yale.edu> 0.9.11
    Only the first signature of a cleartext sig seems to be verified.
    Can't fix it in 1.0 because the code is semi-frozen.
    HMMM: Can't reprodude the bug here - it just works.
a49 16
[ **] #25 1999-10-04  <wk@@gnupg.org> 1.0
    Validity check based on user name is only done when listing a key;
    the key ID based checking (selecting the user ID with the most
    validity) is used in all other cases.  The Edit menu does not have
    a way to disable user ID based validity.
    FIX: 1999-12-03 (1.0.x only)

[  *] #26 1999-11-11
    gpg still does not take UTF8 strings to select a UID.
    FIX: 1999-11-12

[ **] #27 1999-11-12 <oren@@hishome.net>
    Unknown packets (type 17 - photo ID?) mess up the checking
    of self-signature because they are simply ignored.
    FIX: 1999-11-12 (1.0.x only)

d55 3
d59 2
a60 9
[ **] #29 1999-12-01 <karney@@pppl.gov>
    Using a --gen-key on a new user account (w/o ~./gnupg) doesn't pay
    attention to the standard options files, which get's installed
    afterwards.
    FIX: 1999-12-02




d62 1
a62 1
Next #30
@


1.30
log
@See ChangeLog: Sat Nov 13 17:44:23 CET 1999  Werner Koch
@
text
@d38 1
d46 2
a47 1
    gettext bug.  Use GNU gmake as a workaround.
d63 2
a64 1
    a way to disbly user ID based validity.
d72 2
a73 1
    of self-signature becuase they are simply ignored.
d75 4
d80 12
a91 1
Next #28
@


1.29
log
@See ChangeLog: Tue Oct 26 14:10:21 CEST 1999  Werner Koch
@
text
@d50 1
a50 1
    HMMM: Can't reprodude the bug here - it just works.  Check wehther
d63 3
d67 6
a72 1
Next #26
@


1.28
log
@See ChangeLog: Mon Sep 13 10:55:14 CEST 1999  Werner Koch
@
text
@d57 5
d63 2
a64 1
Next #25
@


1.28.2.1
log
@See ChangeLog: Mon Nov 22 11:14:53 CET 1999  Werner Koch
@
text
@d1 2
a2 1
Please see
d4 6
a9 1
    http://www.gnupg.org/buglist.html
d11 4
a14 3
for a list know bugs in GnuPG.	We don't distribute this list anymore
with the package because a more current one with notes in which version
the bug is fixed can be found online.
d16 43
@


1.27
log
@See ChangeLog: Mon Sep  6 19:59:08 CEST 1999  Werner Koch
@
text
@d50 1
@


1.26
log
@See ChangeLog: Tue Aug 31 17:20:44 CEST 1999  Werner Koch
@
text
@d47 11
a57 1
Next #23
@


1.25
log
@See ChangeLog: Fri Jul 23 13:53:03 CEST 1999  Werner Koch
@
text
@d33 2
a34 2
    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"
@


1.24
log
@See ChangeLog: Thu Jul 22 20:03:03 CEST 1999  Werner Koch
@
text
@a31 8
[  *] #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]
    FIX: 1999-07-22 (Fixed the second error, there will be no fix for
    the first one, becuase GDBM is to be replaced)

a41 5

[ **] #19 1999-06-11
    "trustdb transaction too large" with about 500 signatures on a key
    FAEBD5FC.
    FIX: 1999-07-12  (less memory requirement and increased the limit)
@


1.23
log
@See ChangeLog: Mon Jul 12 18:45:57 CEST 1999  Werner Koch
@
text
@d37 2
d40 1
a40 1
[***] #6 1999-02-22 <backes@@rhrk.uni-kl.de> 0.9.3
d45 1
a45 1
    --> IRIX bug still there
d48 1
a48 1
    rndunix hangs on hp/ux.  The problme is related to my_plcose which is
d56 3
d60 1
a60 1
Next #22
@


1.22
log
@See ChangeLog: Sat Jun 26 12:15:59 CEST 1999  Werner Koch
@
text
@d52 1
@


1.21
log
@See ChangeLog: Wed Jun 16 20:16:21 CEST 1999  Werner Koch
@
text
@d29 2
a30 2
     The for loop the exp.date is set before v3 detection?
     [is this bug still alive?]
a52 7
[ **] #20 1999-06-16 <jashley@@yorktown.designlab.ukans.edu>  0.9.7
    Using "addkey" in the edit menu with more than 1 subkey leads to
    "out of secure memory" in some cases.


Next #21

d54 1
@


1.20
log
@See ChangeLog: Tue Jun 15 14:23:10 CEST 1999  Werner Koch
@
text
@d53 3
d57 2
a58 1
Next #20
@


1.19
log
@See ChangeLog: Mon May 31 19:41:10 CEST 1999  Werner Koch
@
text
@d49 6
a55 1
Next #19
@


1.18
log
@See ChangeLog: Sun May 23 20:25:57 CEST 1999  Werner Koch
@
text
@d45 3
d49 2
a50 1
Next #18
@


1.17
log
@See ChangeLog: Sat May 22 22:47:26 CEST 1999  Werner Koch
@
text
@a15 9
[  *] #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
    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)

a44 4

[ **] #17 1999-05-18 <Bodo_Moeller@@public.uni-hamburg.de> 0.9.6
    Import does not detect identical user IDs.
    FIX: 1999-05-22
@


1.16
log
@See ChangeLog: Wed May 19 16:04:30 CEST 1999  Werner Koch
@
text
@d57 1
@


1.15
log
@See ChangeLog: Thu May  6 14:18:17 CEST 1999  Werner Koch
@
text
@d19 5
a23 1
    pgp263ia.
d55 4
a58 1
Next #17
@


1.14
log
@See ChangeLog: Tue Apr  6 19:58:12 CEST 1999  Werner Koch
@
text
@d35 1
a35 1
     [is this bug still there?]
d51 1
a51 18
[  *] #13 1999-04-05
    Trying to generate very large keys fails with a BUG in read_pool()
    FIX: 1999-04-06


[  *] #14 1999-04-05 <anonymous>
    If you use --s2k-cipher-algo twofish, the the program crashes with
    a BUG at line 226 of passphrase.c.
    FIX: 1999-04-06


[ **] #15 1999-04-05
    Hash calculation for subkey bindings is not according to rfc2440 if
    a 4 byte length header is used for the subkey.
    FIX: 1999-04-06


Next #16
@


1.13
log
@./BUGS
@
text
@d53 1
d57 3
a59 7
    If you have the following lines in your "options" file:
      load-extension twofish
      cipher-algo twofish
      s2k-cipher-algo twofish
    and then try to "gpg --gen-key", everything goes along fine until you
    verify your password. Then the program crashes with a BUG at line 226
    of passphrase.c.
d62 1
a62 1
[ **] #15 199-04-05
d65 1
@


1.12
log
@See ChangeLog: Sat Mar 20 12:55:33 CET 1999  Werner Koch
@
text
@d51 20
a70 1
Next #13
@


1.11
log
@See ChangeLog: Sun Mar 14 19:34:36 CET 1999  Werner Koch
@
text
@a49 3
[ **] #12 1999-03-10
    gpg --list-secret-keys --with-colon SEGVs
    FIX: 1999-03-10
@


1.10
log
@See ChangeLog: Wed Mar 10 11:26:18 CET 1999  Werner Koch
@
text
@d47 2
a48 2
    --> I hope I've fixed this: Please, can someone check this.
	I can't reproduce it on the alpha I have access to.
@


1.9
log
@See ChangeLog: Mon Mar  8 20:47:17 CET 1999  Werner Koch
@
text
@d50 6
@


1.8
log
@*** empty log message ***
@
text
@a20 6
[***] #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

d47 1
a47 1
    --> I hope I've fixed this: Please, can check someone it.
a48 29

[  *] #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> 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
@


1.7
log
@See ChangeLog: Tue Mar  2 10:38:42 CET 1999  Werner Koch
@
text
@d11 3
a13 1
(format: severity: [  *] to [***], no, first reported, by, version)
d21 6
d65 19
a83 1

@


1.6
log
@See ChangeLog: Fri Feb 26 17:55:41 CET 1999  Werner Koch
@
text
@d55 1
a55 1
    [26.02.99: temporary fix in encrypt_simple()
a56 7
[   ] #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
    [26.02.99 fixed]
a57 3
[   ] #9 1999-02-25
    Misalignment in md5.c#md5_write.
    [26.02.99 fixed]
@


1.5
log
@See ChangeLog: Thu Feb 25 18:47:39 CET 1999  Werner Koch
@
text
@d45 2
a46 2
    --> I hope I've fixed this: Please, can someone it. I can't reproduce it
	on the alpha I have access to.
d48 1
a48 1
[ **] #7 1999-02-22 <dwpalmer@@dwpalm.jf.intel.com> 0.9.3
d55 1
d57 1
a57 1
[  *] #8 1999-02-25 <kazu@@iijlab.net>
a60 1

d63 1
a63 3
    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.
d65 1
a65 1
[ **] #9 1999-02-25
d67 1
a67 1

@


1.4
log
@*** empty log message ***
@
text
@d67 2
a68 1

@


1.3
log
@See ChangeLog: Wed Feb 24 11:07:27 CET 1999  Werner Koch
@
text
@d56 14
@


1.2
log
@*** empty log message ***
@
text
@d45 2
@


1.1
log
@See ChangeLog: Mon Feb 22 20:04:00 CET 1999  Werner Koch
@
text
@d41 4
d46 7
a52 2


@
