Selecting cipher to generate a key pair

[John W. Moore III]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Robert J. Hansen wrote:
> Smith, Cathy wrote:
>> The customer said they have a proprietary implementation that only
>> supports Blowfish or 3DES for the key.  I'm still trying to find out
>> exactly what that means.
> 
> Okay, that much makes sense now.
> 
> I would suggest adding:
> 
> cipher-algo 3DES
> 
> ... to your .gnupg/gpg.conf file.  This is a sledgehammer solution, and
> not one I'd generally recommend; however, the downsides are pretty
> minimal.  Then encrypt a message using their public key and send it on
> to them.  If they can read it, great.  If they can't, then the problem
> is their proprietary implementation of OpenPGP is shoddy.

Riddle Me this, Robert; _if_ "The Customer" has a requirement that 3DES
must be used [and they are associating it with their Key] then wouldn't
this mean that the *only* preference broadcast by their Key is 3DES?  If
this is the case then wouldn't GPG automatically select this cipher
algorithm by default as the only compatible one between the two parties?
 :-\

JOHN ;)
Timestamp: Friday 01 May 2009, 19:49  --400 (Eastern Daylight Time)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10-svn4987: (MingW32)
Comment: Public Key at:  http://tinyurl.com/8cpho
Comment: Gossamer Spider Web of Trust: https://www.gswot.org
Comment: Homepage:  http://tinyurl.com/yzhbhx

iQEcBAEBCgAGBQJJ+4qAAAoJEBCGy9eAtCsP3o8H/ja6jCWz1bYjjTNXbhLzd5OE
BIgvdlCCsR0Nrm4VY5jGXiOPbk9NYse/43F/DZyQQyyowuRBj3whtpUx6Ueacy+o
u5R6skOdk5AG+HKPVwQ4Zgb4LZhl1Fu4VxOOxWXSW01MnJoxVdtwpj5ylZU5vC7C
EtytAK4HOh1DuQLQYLICupYXhK4TvnbeDRR9s2n6s9n+q1JXFpOEIk5w5d1iJfOk
vn2p8TQ9PrTkMFxweA9gbNoTesH9U5tqmXockb1Mp6JoUz1n56pPWLCyWMxub6f2
GyQNc17RZ/J5qwiY+qK+Mf1L1ONJO3y2zCJfJQxqL0MpODaZFYiOyr3Ws9tVafU=
=A7I6
-----END PGP SIGNATURE-----