Setting Preference for Block Cipher

[Mike Acker]

On 09/07/2013 07:34 PM, gnupg-users-request at gnupg.org wrote:
> Why?  Your preference list makes no sense.
>
>> > TWOFISH CAST5 BLOWFISH 3DES AES AES192 AES256 CAMELLIA128
>> > CAMELLIA192 CAMELLIA256
> GnuPG and PGP will stop as soon as they hit 3DES.  They won't even look
> at the rest of the ciphers in your preference list.  "Okay, Mike likes
> Twofish, but the recipient doesn't support it... then CAST5, but that's
> not supported... then Blowfish, again not supported... hey, 3DES.  3DES
> is *guaranteed* to be supported.  The recipient has to speak 3DES.
> Cool.  We'll choose 3DES and not even bother with the rest of the list."
>
it is important to understand that the specification i have in MY key is
addressed to any party which may be sending to me.  I am essentially
telling the other party: use TWOFISH as my first choice.    Now: if the
sender encrypts the message to more than one recipient then ( if i'm
reading the documention right ) the selection the first supported option
common to both recipients

in the light of new information about NSA and NIST this is an
interesting topic

new information 2013-09-13
<http://www.propublica.org/article/standards-agency-strongly-suggests-dropping-its-own-encryption-standard>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20130915/1f50b37d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20130915/1f50b37d/attachment.sig>