Thunderbird already has a bug which could be interpreted as a request to disable RC2/40 - "S/MIME should not support weak crypto" (https://bugzilla.mozilla.org/show_bug.cgi?id=84213)
Also, here's a thread in which author of gpgsm Werner Koch explains why he doesn't support RC2 and what he thinks about Thunderbird implementation. http://www.nabble.com/gpgsm-1.9.22-supports-no-RC2-Algorithm---tf3581426.html Also, I am using KMail with gpgsm and Thunderbird when I can't decrypt using KMail. So, if anyone needs testing, I can help. Thanks. Paul Hoffman wrote: > At 5:38 PM -0700 4/27/07, Nelson Bolyard wrote: >>Paul Hoffman wrote: >> >>> Proposal: >>> a) Completely turn off the ability to encrypt with RC2/40 unless there >>> is no strong algorithm. >>> b) Every time you are about to encrypt with RC2/40, warn the user, >>> including an explanation of how Tb got to this point in the logic >>> chain. >> >>Patches cheerfully received. :) > > Thought there should be some conversation first... -- Nick _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
