SHA1 being used despite public key preferences

[smu johnson]

Excellent, keep up the great work!  Looking forward to the new version.

On Fri, Oct 29, 2010 at 12:57 PM, David Shaw <dshaw at jabberwocky.com> wrote:

>
> I've made the change.  Incidentally, this was already true for GnuPG 2.0.
>  1.4 now matches the 2.0 behavior of not having any default for
> personal-digest-preferences.
>
> While I was in there, I also made a small change in how MD5 is handled.
>  Previously, if the algorithm selection ran and ended up with MD5 as the
> winning algorithm, GnuPG would replace it with SHA-1 (if available).  Now,
> as long as there is at least one other digest available, MD5 is simply
> removed from the available algorithm list.  This means that the next-highest
> ranked algorithm will be chosen, instead of forcing it to SHA-1.
>
> David
>
>


-- 
smu johnson <smujohnson at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20101029/8a959b34/attachment.htm>