Fri, 26 May 2000 13:18:04 -0700 (PDT)
-----BEGIN PGP SIGNED MESSAGE-----
On Fri, 26 May 2000, Pete Chown wrote:
> Well, I've just managed to get pgp interworking with gnupg the way I
> want after a painful day that ended up with me running gdb on pgp
> (6.5.1). As a few people here have had similar problems I thought I
> would write it up -- it should provide another data point.
Unfortunately, I doubt anyone will read this in a few weeks. Werner posted
this info back in January, I believe:
gpg --s2k-cipher-algo=CAST5 --s2k-digest-algo=SHA1 --compress-algo=1
- --edit-key keyid
where keyid is your keyid. Remove the password, then do:
gpg --export-secret-key --no-comment -a keyid >keyid_secert.asc
Then copy it to the windows machine, add it, restore the passphrases (on
gpg --edit-key keyid
> Unfortunately now pgp would ask for a passphrase and would not accept
> anything that I typed in. The original key had been created without a
> passphrase. This was the point where I built pgp from source and then
> ran gdb on it. It turned out that the secret key hadn't imported
> correctly and this error condition is not handled right -- it looks
> like a definite pgp bug.
The problem is you are using as your s2k cipher Blowfish, which PGP does
not and will not support.
System Administrator | "It's a nice day
Technology Consultant | to start again."
icq.. 10735603 |
pgp.. finger://ns.quickie.net/rabbi | --Billy Idol
-----BEGIN PGP SIGNATURE-----
Comment: OpenPGP Encrypted Email Preferred.
-----END PGP SIGNATURE-----