Setpref is not working or is it a bug or something?

[Robin Mathew Rajan]

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

Hi bro, :)

Thanks for correcting me. 

Regards! :)
Robin Mathew Rajan


On 29-11-2014 AM 08:57, Robert J. Hansen wrote:
>> You can delete these values from your current gpg.conf.
>>
>> s2k-digest-algo SHA256 s2k-cipher-algo AES256 cert-digest-algo SHA256
>> digest-algo SHA256
>>
>> Reason 1: Those values are used when options like 
>> 'personal-cipher-preferences', 'personal-digest-preferences' and 
>> 'personal-compress-preferences' are not given! But here, you already 
>> gave those three options already.
> 
> This isn't quite true.  personal-*-preferences won't affect s2k
> preferences or cert-digest-algo.  However, you're absolutely correct to
> advise against using cipher-algo or digest-algo.
> 
> (I *think* I'm right on this, but I can't promise I am, nor have I done
> a quick empirical test to check.  Take the preceding with a grain of salt.)
> 
>> Reason 2: Those values are known to break the OpenPGP standard.
> 
> Some of them are serious problems (digest-algo and cipher-algo).  The
> others are mostly safe.  s2k is only used by the user on their own
> machine, so there isn't much concern about interoperability with other
> OpenPGP clients.
> 
>> That's the same OpenPGP does. OpenPGP standard is just a reference 
>> model. Anyone can modify it and include unique features. But it's
>> not necessary to be those 'unique features' to be included in every 
>> OpenPGP implemented products. But when it comes to communicating
>> each other, there comes the problem if there's no common standard
>> rule.
> 
> Those who are concerned about OpenPGP conformance should add "openpgp"
> to the end of their gpg.conf file.  :)
> 
>> But at the same time, these settings might be incompatible with
>> older softwares.
> 
> Nope!  The preference list you gave will not cause troubles with any
> OpenPGP application, not even old PGP 5.x.  If there's no preference
> list on your recipient's public key (which does happen, from time to
> time), OpenPGP will gracefully degrade to use SHA-1 and 3DES.  SHA-1 is
> getting pretty long in the tooth, but 3DES is still solid as a rock.
> 
> My usual joke about 3DES -- which, like most of my jokes, is a way of
> telling truth with a laugh -- is that 3DES has all the beauty of a
> Soviet workers' housing bloc, all the aesthetics of the Socialist
> Realism school of art, and yet has been turning brilliant young
> cryptanalysts into burned-out alcoholic wrecks for the last 35 years.  :)
> 
> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-users
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJUenyNAAoJEJyRZAJNoXmulPYP/jWu0Om3Jt2FIZwWc65cPlbz
odJrDeQvzwJ0b03xtJy5B1e42cIRfSZVNkLpUP8ajxdbH/ISgraXtEmhZwyZwIfg
Rnx986Mnrb5kT9eY1JbBLYVm20Exq9nwkrvoMjbWnJESJxbqcNYKYcAIjZkRAHqd
ow3um/OGlY/HS+t/0Q92d6TRfaLkJxhmIw6EqwutFuQ44MUd3no9I5J0sn1CnGXG
0twX2h6IXAlzPEBJz2eMSjpmwEDVLHzzMw7UixVc8jOjlf+uk1XboZZgxiaEXZAq
ydycXICFI8rVtQQmKDgVuBQvFLUYC4ZInKFDM/qTEgi4r1bs3XGzoBk2y8BJxep+
q0lDeNvXDyZXRXms0Ga0aWUaJ29pfS95/nKqaF7/ndFNOVNS3/oXgAuS2uRs9s5l
BRp2wWb7S82H5ueLffhNAvHTgq2vffDglNrm+TrAHyUw48H0Fsx0TsVjlgotAx+x
5yGcf5MzAxlpEa4FpcUZN1xjto3sh5/Q57bCFAsYoVbbkuyTsvPBD1FUzwY8SlC7
R1M7c0xLhO96NsKEQVdz7HQW0yE2jF4ZBsBcSUc7wzIvCEIKdtO6U9mQYOhJ9Fx1
HjUTRnLlPv3h+/D4GR4CQjER6LF5xGjXMaSWl6v83uUsVTL4tSKo/ZbgLszSh3TD
rGhlmAvGGfwFpL8zf0nS
=HQCO
-----END PGP SIGNATURE-----