Known bugs in PGP 2.6.3i|
The following is a list of known bugs in PGP 2.6.3i, and how to correct them. If you think you have discovered a new bug, please mail the details to email@example.com.
PGP 2.6.3(i)a patches available
Click here to download the latest bug-fixes for PGP 2.6.3(i). (Sorry, source code only!)
PGP ignores long form of TZ variable
SET TZ=SSS[+|-]nDST,sm,sw,sd,st,em,ew,ed,et,shiftHowever, most PGP compilations simply ignores everything after the first comma, which means that PGP will always switch to DST at 01:00 on the first Sunday in April, and back again at 02:00 on the last Sunday of October. This may not be correct for all countries (and certainly not if you're in the southern hemisphere).
PGP can't handle pass phrases with accented characters
A piece of advice: don't use any such characters. :-) A pass phrase written in one character set or code page would probably not work in another anyway. I think this "bug" was introduced somewhere around version 2.6. If you have an old key with national characters in the pass phrase, change the pass phrase to plain ASCII before upgrading to 2.6.3i.
Incorrect command line parsing with Borland C (MS-DOS)
pgp -seat +comment="Would you send mail without an envelope?" msg.txt schumachershould be written as:
pgp -seat "+comment=Would you send mail without an envelope?" msg.txt schumacher
Text files treated as binary (all platforms)
if (lfctr>132) return FALSE; /* line too long. Not a text file*/But please note that text files with such long lines normally don't get through email intact, resulting in a bad signature.
Cannot generate keys (Macintosh)
Compiling problems (various Unix platforms)
Undefined strdup() function
if (!(new[entrynum++] = strdup(tempbuf)))to:
if (!(new[entrynum++] = store_str(tempbuf)))
Then remove the 'static' declaration from store_str() in keymaint.c. If you're using an ANSI compiler, you'll have to add the prototype for store_str() in keymaint.h, too:
char *store_str(char *str);
This bug is unique to PGP 2.6.3i, but has been fixed.
This bug is inherited from MIT PGP 2.6.2 and is present in all versions of PGP.
[ PGPi Home > Documentation > Known bugs in PGP > PGP 2.6.3i ]