added a note with the upstream CR for the smime_keys manpage request

[software/mutt-debian.git] / debian / patches / upstream / 514960-certificate-insecure-algorithm.patch

diff --git a/debian/patches/upstream/514960-certificate-insecure-algorithm.patch b/debian/patches/upstream/514960-certificate-insecure-algorithm.patch
index f0292f29f26b8f3d746913dd0bfd4c26aa5a3f35..0aa4096d8bb2457284d53b60f0d5d516e1de6264 100644 (file)
--- a/debian/patches/upstream/514960-certificate-insecure-algorithm.patch
+++ b/debian/patches/upstream/514960-certificate-insecure-algorithm.patch
@@ -1,3 +1,9 @@
+The new version of gnutls introduced this new option which mutt did not 
+know about, if the cert is signed with an insecure algorithm (md5) it will
+set a particular bit; if the cert is in the cache of the user we will
+unset all bits so this has to be unset as well
+See http://bugs.mutt.org/3229 and http://bugs.debian.org/514960
+
 --- a/mutt_ssl_gnutls.c
 +++ b/mutt_ssl_gnutls.c
 @@ -614,6 +614,13 @@