Re: April CA Communication: Results

2017-05-16 Thread Peter Gutmann via dev-security-policy
Jakob Bohm via dev-security-policy writes: >Indeed, I strongly suspect Microsoft *customers* combined with Microsoft >untrustworthiness (they officially closed their Trustworthy Computing >initiative!) may be the major hold out, specifically: > >1. [...]

Re: April CA Communication: Results

2017-05-15 Thread Jakob Bohm via dev-security-policy
On 15/05/2017 15:53, Doug Beattie wrote: ... Yes, it is certainly a bit dated. Outlook 2013 and 2016 are not listed along with more recent versions of iMail and Thunderbird. I believe the point of the document was only to list what was needed to get SHA256 compatibility. So for each

Re: April CA Communication: Results

2017-05-15 Thread urijah--- via dev-security-policy
It's useful to note that Outlook 2007 leaves extended support on October 10. (That deadline has been extended a few times, I believe, but this should be the final date.) https://support.microsoft.com/en-us/help/3198497/office-2007-approaching-end-of-extended-support On Monday, May 15, 2017 at

RE: April CA Communication: Results

2017-05-15 Thread Doug Beattie via dev-security-policy
.org > Subject: Re: April CA Communication: Results > > On 2017-05-15 15:38, Kurt Roeckx wrote: > > On 2017-05-15 15:26, Gervase Markham wrote: > >> On 15/05/17 14:19, Doug Beattie wrote: > >>> https://support.globalsign.com/customer/portal/articles/12163

Re: April CA Communication: Results

2017-05-15 Thread Kurt Roeckx via dev-security-policy
On 2017-05-15 15:38, Kurt Roeckx wrote: On 2017-05-15 15:26, Gervase Markham wrote: On 15/05/17 14:19, Doug Beattie wrote: https://support.globalsign.com/customer/portal/articles/1216323 Thanks, Doug. There's no date on that doc - are you able to say when it was written? It says: Last

Re: April CA Communication: Results

2017-05-15 Thread Kurt Roeckx via dev-security-policy
On 2017-05-15 15:26, Gervase Markham wrote: On 15/05/17 14:19, Doug Beattie wrote: https://support.globalsign.com/customer/portal/articles/1216323 Thanks, Doug. There's no date on that doc - are you able to say when it was written? It says: Last Updated: Aug 26, 2013 11:24AM EDT Kurt

Re: April CA Communication: Results

2017-05-15 Thread Jakob Bohm via dev-security-policy
On 15/05/2017 15:26, Gervase Markham wrote: On 15/05/17 14:19, Doug Beattie wrote: https://support.globalsign.com/customer/portal/articles/1216323 Thanks, Doug. There's no date on that doc - are you able to say when it was written? Gerv I believe it is a "live" doc, that was regularly

Re: April CA Communication: Results

2017-05-15 Thread Gervase Markham via dev-security-policy
On 15/05/17 14:19, Doug Beattie wrote: > https://support.globalsign.com/customer/portal/articles/1216323 Thanks, Doug. There's no date on that doc - are you able to say when it was written? Gerv ___ dev-security-policy mailing list

RE: April CA Communication: Results

2017-05-15 Thread Doug Beattie via dev-security-policy
emo.com>; mozilla-dev-security- > pol...@lists.mozilla.org > Subject: Re: April CA Communication: Results > > On 15/05/17 14:07, Jakob Bohm wrote: > > 1. Microsoft's e-mail clients were very late to accept stronger > > signature algorithms for e-mails (including e-mails sent

Re: April CA Communication: Results

2017-05-15 Thread Gervase Markham via dev-security-policy
On 15/05/17 14:07, Jakob Bohm wrote: > 1. Microsoft's e-mail clients were very late to accept stronger > signature algorithms for e-mails (including e-mails sent by users of > non-problematic e-mail clients). I believe Globalsign's page about > SHA256-transition for customers provides a

Re: April CA Communication: Results

2017-05-15 Thread Kurt Roeckx via dev-security-policy
On 2017-05-15 13:40, Gervase Markham wrote: * (Q13) Many CAs plan to stop issuing SHA-1 S/MIME by the end of this year. CAs without a firm date are: Comodo, GlobalSign, SECOM, TWCA, and Visa. A couple of these CAs hint that an industry deadline to stop would help their customers see the need to

April CA Communication: Results

2017-05-15 Thread Gervase Markham via dev-security-policy
With two exceptions (neither of which have the websites trust bit set), all answers are now in from the April 2017 CA Communication. You can find links to the answers here: https://wiki.mozilla.org/CA/Communications#April_2017_Responses Some highlights for the community's attention: * (Q1) It