[Enigmail] New GnuPG 2.0.27

Enigmail User enigmail_user at glib.com
Sun Mar 22 01:34:21 CET 2015


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

On 3/21/2015 11:44, Onno Ekker wrote:
> On 21-3-2015 16:39, Enigmail User wrote:
>> On 3/21/2015 06:36, Olav Seyfarth wrote:
>>> Hi Patrick,
>> 
>>>> I'm thinking about adding "--allow-weak-digest-algos" to the
>>>> GnuPG parameters if GnuPG > 2.0.27 is detected. Would you
>>>> think this is a good idea to get rid of the problem -- or
>>>> this just postponing the problem?
>> 
>>> Please don't. MD5 IS an issue and should not be trusted by
>>> default. Same line of thinking as with the red warning about
>>> unencrypted messages. We should provide (or link to) a help/FAQ
>>> page how to solve it.
>> 
>> Is there any way in GPG to change the digest used with an older
>> key? I have a SHA-1 digest in a key that I use, and I'd like to
>> make that SHA-256 if possible.
>> 
> You can add a new subkey to your key with the digest you want. It's
> not possible to change an existing subkey. Just open gpg --edit-key
> <yourkey> and use addkey

Okay, thanks. I've done that.

Do I need to send my public key to the key servers again now?
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVDg4KAAoJEFxfeKGiIGeDXfYP/2bzehUY+JHR+i6RAjvZpjwB
Tb2ZT9zt+70ziPxug1uSuOoSva4KbaoC2lwFd5vKY8FHoo7XUAqz8k1zqgV6CcS3
Z1rZTqNFrKIvP1a0jiUO4IDjJLTe+VX5zjGT+dCqT+28AXdMYFOa5Xcvncmi5PJr
TbXhw4KW6V4L4+/VCpPEtjuqiDPCUh+BcMS9AwPRWfDZhzR2ctPZ8mzXtCH2umEp
+TaIJFBufZpawzSgeE0vy58QyMPvFuRgYDVlpIPbl27LT8HanSbBn5C6KVTdr9pY
MPpFPpQKtTPZXNypRF2PwDUJwHUXFlujCOdlnobqRAwZlLWWU3rUMtKoqTomopVp
oDXM+Qh5WkNmPaWnsQeyKamOYPxzUc00wRnLlkSIb26mSkVOT3//pNX5PjQ+R9qx
Tqggr/dIe02oXj3yRVgMfCAAfHJNfuu3jGSjMYl11ovL0YHiEewsW6wqJ/VfA8tP
RbNpSLrfXrMeqas3EXdFTO35uq9D2LOooHh0HZlK0ZX3W3tcV38gOuzuk/DVQLyu
GkfzLLIn28bi+3TWVWljcAtNdu9Sd1x3db+rqgFUajk2eTy0s5pAqjwlCo+WcYDa
oGBvbjg/HSy/Jhj7kwk2C1ErxL/llcC4spJ6sk9EHFXBnjPs/xReHSgJ2uj5KG1X
wLBmaufiKR2Ke9T4oUs+
=5uZ2
-----END PGP SIGNATURE-----



More information about the enigmail-users mailing list