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
Onno _______________________________________________ enigmail-users mailing list [email protected] To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
