Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Bob Henson
On 20/03/2015 10:01 pm, Olav Seyfarth wrote: installed GnupG 2.0.27, via Gpg4Win 2.2.4 reason is, that GnuPG 2.0.27 errors out if it detects keys using MD5. Workaround: use allow-weak-digest-algos in Enigmail or gpg.conf Is there a method to search for such keys? I definitely *don't know

Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Patrick Brunschwig
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 21.03.15 10:57, Olav Seyfarth wrote: Hi Bob, Deletion was a shade more complex as two old Thawtes keys had private keys, but all is now well. Thanks again, So, how did you solve that? I also had two secret keys, now removed. I'd like to

Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Enigmail User
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 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

Re: [Enigmail] enigmail's new handbook - for 1.8 : smartcard reset

2015-03-21 Thread Ludwig Hügelschäfer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Philip, On 19.03.15 22:16, Philip Jackson wrote: The listing in the new handbook appears to be the old instructions which WK says do not always work. Thanks for reporting! Is now corrected in my source. We'll collect feedback for a time and

Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Onno Ekker
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

[Enigmail] Error saving draft

2015-03-21 Thread Onno Ekker
Hi, After upgrading to Enigmail 1.8 I get an error on Windows 8.1 Thunderbird 31.5.0 saying Unable to save your message as draft./Please verify that you Mail Newsgroups account settings are correct and try again. In the Error Console I see the following messages: Error: Component is not

Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Bob Henson
On 21/03/2015 9:57 am, Olav Seyfarth wrote: pre wrap Hi Bob, /preblockquote type=citepre wrap Deletion was a shade more complex as two old Thawtes keys had private keys, but all is now well. Thanks again, /pre/blockquotepre wrap So, how did you solve that? I also had two secret keys, now

Re: [Enigmail] Error saving draft

2015-03-21 Thread Ludwig Hügelschäfer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 21.03.15 11:46, Onno Ekker wrote: Hi, After upgrading to Enigmail 1.8 I get an error on Windows 8.1 Thunderbird 31.5.0 saying Unable to save your message as draft./Please verify that you Mail Newsgroups account settings are correct and

Re: [Enigmail] Error saving draft

2015-03-21 Thread Onno Ekker
On 21-3-2015 11:46, Onno Ekker wrote: Hi, After upgrading to Enigmail 1.8 I get an error on Windows 8.1 Thunderbird 31.5.0 saying Unable to save your message as draft./Please verify that you Mail Newsgroups account settings are correct and try again. In the Error Console I see the

Re: [Enigmail] Error saving draft

2015-03-21 Thread Onno Ekker
On 21-3-2015 12:26, Ludwig Hügelschäfer wrote: On 21.03.15 11:46, Onno Ekker wrote: Hi, After upgrading to Enigmail 1.8 I get an error on Windows 8.1 Thunderbird 31.5.0 saying Unable to save your message as draft./Please verify that you Mail Newsgroups account settings are correct and

Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Bob Henson
On 21/03/2015 10:36 am, 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

Re: [Enigmail] (Bug) Enigmail notices illegible in some color schemes

2015-03-21 Thread Patrick Brunschwig
On 20.03.15 15:52, Matthew Woehlke wrote: The signature verification/warning banner at the top of messages is illegible when using a light-on-dark color scheme; see attached. Hard-coding the foreground color as well as the background color would be an improvement, but please note that some

Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Olav Seyfarth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Robert, the point was: is it possible to further use a key that has/had MD5 and now throws a warning by modifying it. If not, then the only way seems to be to delete the key - if one doesn't want to /allow-weak-digest-algos/ . Olav - -- The

Re: [Enigmail] enigmail's new handbook - for 1.8 : smartcard reset

2015-03-21 Thread Philip Jackson
Hi Ludwig : On 21/03/15 16:26, Ludwig Hügelschäfer wrote: We'll collect feedback for a time and publish a corrected version afterwards. Another comment connected with smartcard usage. In the new handbook, next to last paragraph on page 98, it says : The card is used to store the actual

Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Robert J. Hansen
the point was: is it possible to further use a key that has/had MD5 and now throws a warning by modifying it. If not, then the only way seems to be to delete the key - if one doesn't want to /allow-weak-digest-algos/ . D'oh -- my bad. By old key I thought the poster meant, you know, an old

Re: [Enigmail] New GnuPG 2.0.27

2015-03-21 Thread Enigmail User
-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.