In linux using Gnupg & Kgpg w/ pgp6 compatibility set in kgpg to
create the key pair. In the gpg options file I also have compress-
algo 1, cipher-algo cast5 set.

On the command-line I create the nym reply blocks using --pgp6
option when encrypting at every step.

When I get the confirmation back, everything will decrypt ok using
gpg under linux. No problems.

If I boot into Windows and use Pgp 6.58ckt, the conventional pass-
phrase decrypt fine but when it gets to decrypting the final key pair
encrypted part, it always returns a "Bad Packet" error.

Is there a gpg option I could set which would allow Pgp6.5.8 to be
able to decypt the key pair part?

BTW, Pgp6.5.8 does not balk when I import the gpg key. And all the
properties look OK under Pgp6.5.8.

Thanks.

[ Post a follow-up to this message ]

On Wed, 31 Jan 2007 13:55:34 +0000
Tig <tigger@nowhere.invalid> wrote:

> In linux using Gnupg & Kgpg w/ pgp6 compatibility set in kgpg to
> create the key pair. In the gpg options file I also have compress-
> algo 1, cipher-algo cast5 set.
>
> On the command-line I create the nym reply blocks using --pgp6
> option when encrypting at every step.
>
> When I get the confirmation back, everything will decrypt ok using
> gpg under linux. No problems.
>
> If I boot into Windows and use Pgp 6.58ckt, the conventional pass-
> phrase decrypt fine but when it gets to decrypting the final key pair
> encrypted part, it always returns a "Bad Packet" error.
>
> Is there a gpg option I could set which would allow Pgp6.5.8 to be
> able to decypt the key pair part?
>
> BTW, Pgp6.5.8 does not balk when I import the gpg key. And all the
> properties look OK under Pgp6.5.8.
>

I've had pretty much the same problem on occasion. My sieve of a brain can't
remember what causes the problem, maybe someone else will pitch up with the
answer. I seem to remember something about the comments header, but that mig
ht
not be it. For your own tests, if you encrypt a text message in linux and tr
y
to decrypt it in Windows using PGP, does it decrypt?

The conventional passphrases, of course, are not encrypted using 'your' key,
 so
no surprise that they decrypt okay.

I think the best solution is to use GnuPG in Windows. Of course that's no go
od
if you're trying to use JBN, as it doesn't support use of GPG; but will work
 if
you decrypt yourself. I know Panta-admin worked at getting JBN to work in WI
NE
under linux, but I don't know if he used GPG with it or PGP. I don't know ab
out
QS as I've never used it.

I also found differences between different nym-servers in this regard, but Y
MMV.

[ Post a follow-up to this message ]

Tig wrote:
[snip]
> If I boot into Windows and use Pgp 6.58ckt, the conventional pass-
> phrase decrypt fine but when it gets to decrypting the final key pair
> encrypted part, it always returns a "Bad Packet" error.
>
> Is there a gpg option I could set which would allow Pgp6.5.8 to be
> able to decypt the key pair part?

What ckt version are you using?

-----BEGIN PGP SIGNED MESSAGE-----

-----------------------------------------------------------
PGP 6.5.8ckt - Build07(Updated) - Read me file - 03/17/2002
-----------------------------------------------------------

This is the 6.5.8ckt Build07 binary distribution.
The source code corresponding to this build may
be downloaded separately from http://www.ipgpp.com/

What's New:

1) Fixes to the PGPdisk driver so that PGP disk
volumes will appear in the Windows XP explorer.
2) Fixes to the PGPdisk driver so that PGP disk
volumes may be formatted in the windows XP
environment.
3) Fixes to the MS Outlook PGP plugin so that
the decrypt button will work with Outlook
2000 and Outlook XP.
4) Graceful OpenPGP MDC packets handling.
5) Nuking of proprietary packets generated by non
compliant OpenPGP implementations.
6) Handling of signature verification where the
signing key is a sub-key.
7) Handling of decryption of messages where the
decryption sub-key is revoked or expired.
8) Fixes to the Keygen Wizard so that RSA v3 keys
will be properly generated with IDEA as the default
cipher.
9) Warning in Keygen Wizard removed when generating
RSA v4 keys.
10) Warning removed when exiting PGPtray.
11) Additional hashes support contributed by Disastry:-
SHA256, SHA384, and SHA512.
12) Preferred hash algorithm is now based on public
key algorithm.  These may be set in the "Preferred
Hashing algorithm" combos in the Advanced tab of
the PGP preferences dialog.  Many thanks to Disastry
for this valuable feature.
13) "Change Key Preferences" of v4 keys, namely change
the expiry date and/or the preferred ciphers of
an existing v4 key.  This feature may be accessed
by clicking on the "Change Key Preferences..." button
in the Key properties dialog.  This feature was also
contributed by Disastry.
14) Display of un-implemented hash algorithm by name instead
of by algorithm ID, in PGPKeys and the verification blocks.
The program is currently aware of the following un-implemented
hash algorithms: TIGER192, HAVAL-5-160, and HAVAL-5-256.
15) NAI's "PGPsdk Key Validity Vulnerability" patch applied
(Hotfix0904 http://www.pgp.com/downloads/pgpsdk-patch-download.asp).
16) Compiled with Intel RNG support.  The program will use the Intel
RNG if the Intel Security Driver is installed.  If you have
an Intel chipset based motherboard with an Intel firmware hub
(usually an 810 class or better Intel chipset) then you may
download the Intel Security Driver from here:-
http://www.intel.com/design/softwar...rm/security.htm
After installing the above, this build of PGP will use
the Firmware Hub's hardware Random Number Generator.
17) Ported the installer/un-installer to the InstallShield 6.31
platform, this should provide more reliability.  The installer
will attempt to perform an un-install if it detects an existing
PGP 6.5.x installation, it will then proceed to install this build.
It is strongly recommended that the user re-boots to complete
the installation.  Should the installer detect some version
of PGP other than 6.5.x installed, it will not proceed.  In this case
please follow the installation procedure below.  The installer is
now language aware, I hope.
18) Other minor fixes, and miscellaneous cosmetic changes.
19) Updated the deflate modules to use zlib 1.1.4 instead of zlib 1.1.3.
20) Compiled using MS SDK November 2001, Numega DriverStudio 2.6.

Please do not install the Outlook Express plugin on a windows 2k/XP
box, as this is known to cause random crashes of the system.

For proper installation please apply the following instructions carefully:-
1) Un-install whatever build of PGP you have.
2) Re-boot.
3) Using Regedit navigate to this key:

For Windows 9x/Me machines:-
& #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Control\SessionManager\Know
nDLLs]

For Windows NT/2K/XP machines:-
& #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Control\Session Manager\Kno
wnDLLs]

4) Should you find any values pertaining to PGP under the above key
please delete them, otherwise proceeds to step 6.
5) Re-boot.
6) Delete, if any, PGP*.* in your windows or windows system directory.
7) Install Build 07.
8) Re-boot.

This build is by no means complete, it is released with the
hope that users will provide the necessary feedback so as
to enable me to better resolve any issues in subsequent builds.
Should you find any problems which are build specific, or should
you have any requests or recommendations, please do not hesitate
to contact me matic@cyberia.net.lb

Best Regards,

And Happy Encrypting,

Imad R. Faiad
-----BEGIN PGP SIGNATURE-----
Version: 6.5.8ckt http://www.ipgpp.com/

iQEVAwUBPJSs4rzDFxiDPxutAQE5fAf/bERlWj5GNqDD1xgDMXkVgrDq3Lz35uig
 sfhgAV3anaLI1cpNfwjn45oFOTUKueuLOK3IU9sx
7c0PmeKU0fR4Mgwv0dn27umH
08epCXoqastz6Ggv+9IFLNk+bP2ldkoXwhX/RFuHW8aiMqWOXljhWomi7/NDUdMs
 AUe4St7HjwgLEU3uzJ+6SpCw5SW7HBu0vCX3e4yB
+leLgZxpWaEt01cLIJmIyOmr
 08Gqn01gMwfzfNMXnkgl5U1EJcxDP0JL+lLyCuOw
i4TihPksbP7eI2r5pXBXC0Qx
h4OWNHVHV/ KZUU1tmJvNpOAzRG4baZ2dIIQeFjDNyaufU42sp5
EFBA==
=XeRX
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
--
Life will not break your heart
It'll crush it

- Rollins Band

[ Post a follow-up to this message ]

Anonymous wrote:

snip
>I've had pretty much the same problem on occasion. My sieve of a brain can'
t
>remember what causes the problem, maybe someone else will pitch up with the
>answer. I seem to remember something about the comments header, but that mi
ght
>not be it. For your own tests, if you encrypt a text message in linux and t
ry
>to decrypt it in Windows using PGP, does it decrypt?

Yes encrypting something with my key in linux then decrypting within
Window & PGP does decrypt okay. FWIW - Imad's PGP 6.5.8ckt build09b2.

The nymserver I was using is Komite. For a test I'll try one of the other
nym-servers this weekend.

Thanks for the input.

[ Post a follow-up to this message ]

Thomas J. Boschloo wrote:

>Tig wrote:
>[snip] 
>
>What ckt version are you using?

Imad's PGP 6.5.8ckt build09b2. As per the other reply, I did a test by
encrypting some text in linux-gpg and it did decrypt okay using Pgp
in Windows. It just may be something in the way Komite encrypts it's
messages. Will try another nym-server this weekend to see if there
is any difference.

Thanks, Thomas.

[ Post a follow-up to this message ]

Tig wrote:

>In linux using Gnupg & Kgpg w/ pgp6 compatibility set in kgpg to
>create the key pair. In the gpg options file I also have compress-
>algo 1, cipher-algo cast5 set.
>
>On the command-line I create the nym reply blocks using --pgp6
>option when encrypting at every step.
>
>When I get the confirmation back, everything will decrypt ok using
>gpg under linux. No problems.
>
>If I boot into Windows and use Pgp 6.58ckt, the conventional pass-
>phrase decrypt fine but when it gets to decrypting the final key pair
>encrypted part, it always returns a "Bad Packet" error.

While writing a Nym creation & maintenance program for Linux, I ran into
the same 'Bad Packet' error. To remedy the situation you need to change
the compression algo to Z1 (zip) by editing the key in a console. I have
tried setting the same options in the .gnupg/options file, however, when
generating a new keypair, they always have the default settings when I
check the key prefs. I'll will include some example output below so you
can get an better idea of what the procedure will look like. Also, a list of
codes and their corresponding meanings.

Basics steps are:
gpg --edit-key keyname    (starts the edit key session)
Command> showpref       (just shows a more readable form of out put)
Command> pref                (the less readable code you will change)
Command> setpref           (set the new parameters for the key)

Here is a real example below set to use: CAST5, SHA1& ZIP

[fakename@localhost ~]$ gpg --edit-key del@nowhere.com

gpg (GnuPG) 1.4.2.2; Copyright (C) 2005 Free Software Foundation, Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

Secret key is available.

pub  1024D/F58DDC55  created: 2007-02-11  expires: never       usage: CSA
trust: ultimate      validity: ultimate
sub  2048g/22C6C41B  created: 2007-02-11  expires: never       usage: E
[ultimate] (1). Delete <del@nowhere.com>


Command> showpref
pub  1024D/F58DDC55  created: 2007-02-11  expires: never       usage: CSA
trust: ultimate      validity: ultimate
[ultimate] (1). Delete <del@nowhere.com>
Cipher: AES256, AES192, AES, CAST5, 3DES, IDEA
Digest: SHA1, SHA256, RIPEMD160
Compression: ZLIB, BZIP2, ZIP, Uncompressed
Features: MDC, Keyserver no-modify


Command> pref
pub  1024D/F58DDC55  created: 2007-02-11  expires: never       usage: CSA
trust: ultimate      validity: ultimate
[ultimate] (1). Delete <del@nowhere.com>
S9 S8 S7 S3 S2 S1 H2 H8 H3 Z2 Z3 Z1 [mdc] [no-ks-modify]


Command> setpref S3 H2 Z1
Set preference list to:
Cipher: CAST5, 3DES
Digest: SHA1
Compression: ZIP, Uncompressed
Features: MDC, Keyserver no-modify
Really update the preferences? (y/N) y

You need a passphrase to unlock the secret key for
user: "Delete <del@nowhere.com>"
1024-bit DSA key, ID F58DDC55, created 2007-02-11


pub  1024D/F58DDC55  created: 2007-02-11  expires: never       usage: CSA
trust: ultimate      validity: ultimate
sub  2048g/22C6C41B  created: 2007-02-11  expires: never       usage: E
[ultimate] (1). Delete <del@nowhere.com>

Command> quit
Save changes? (y/N) y
[fakename@localhost ~]$
----------------------------------------------------------------------------
-------------------------------------

Here are the codes:

Pref Code (n)  Algorithm (name)
S1* IDEA
S2  3DES
S3  CAST5
S4  Blowfish
S7  AES (128)
S8  AES192
S9  AES256
S10  Twofish
* only with IDEA module.

Digest (Hash) Algorithms
Pref Code (n)  Algorithm (name)
H1   MD5
H2   SHA1
H3   RIPEMD160
H6+  TIGER192
H8*  SHA256
H9*  SHA384
H10* SHA512
* only with  SHA-2 module & SHA-2 patch
+ only with TIGER module

Compression Algorithms
Pref Code (n)  Algorithm (name)
Z0  uncompressed
Z1  ZIP (RFC 1951)
Z2  ZLIB (RFC 1950)

The default preferences for GPG keys are:
Algorithm Type  Preferences (in order)
Symmetric cipher  AES (128), CAST5, 3DES, IDEA
Hash  SHA1, RIPEMD160
Compression  ZLIB, ZIP
----------------------------------------------------------------------------
-------------------------------------

Good luck & happy decrypting ...in Linux & Windows 

Ciao,
Gia

[ Post a follow-up to this message ]

Gia wrote:

<big snip>
>
>Good luck & happy decrypting ...in Linux & Windows 

First... thanks to all for the replies and helpful suggestions!

In my case, it ended up being the Z* parameter that was causing the Bad
Packet error. Mine was set to use zlib instead of zip. Everthing decrypts
fine now in both OSs.

Thanks again, people!

Tig~

[ Post a follow-up to this message ]