cipher algorithm 9 not found in preferences

Nick Andriash Nick Andriash <>
Sun Mar 11 01:04:16 2001

Hash: SHA1

On March 10, 2001 at 3:49:55 PM, Karol Pietrzak wrote:

> if i remember correctly, this error is caused by gnupg 1.0.4 if
> the rijndael cypher algo is used. it's nothing to get worried
> over, and has already been fixed in cvs.
That is what I thought Karol. I've searched the archives, but it must be listed under a different subject. Can you recall how far back the discussion was, and what the subject may have been? I presume the "cvs" is an interim release, and the problem will have been dealt with in 1.0.5, or whatever the new release will be? Another question I have Karol, is that if I generate a new Key pair in GPG using Rijndael-256 as my preferred algorithm, do you know why, if I export that Key into PGP, it reports the algorithm used as AES-128? Perhaps you could you take a look at my Options file, and let me know if anything is amiss or if I have some redundancy that may be causing that: default-key 0x7BA3FDCE default-recipient-self encrypt-to 0x7BA3FDCE quiet escape-from-lines cipher-algo RIJNDAEL256 digest-algo SHA1 compress-algo 1 force-v3-sigs load-extension idea.dll s2k-digest-algo sha1 s2k-cipher-algo cast5 Thanks so much for your response. Nick -=N.J. Andriash | Vancouver, B.C. Canada=- [ TB! v1.52 Beta 1 | Win 98 SE 4.10 2222 A ] [ GnuPG v1.0.4-1 (MingW32) | Key ID: 0x7BA3FDCE ] __________________________________________________ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4-1 (MingW32) - GnuPGshell v1.60 Comment: Join PGP-Basics: iD8DBQE6qsCHxQKEdHuj/c4RAiO4AKDYacqWNVNO8NpZK953Z63ymdJZ8wCcD0pH u0sdSz3ZaKtg7p/xbs8G5cA= =QR8g -----END PGP SIGNATURE-----