I believe you are confusing two different things. 1. Whether the browser supports SHA-1 certificates at all. 2. Whether the browser supports SHA-1 certificates signed after Jan 1 2016 (The CA/BF Baseline Requirements forbid this, so no publicly valid certificate should fall into this category).
It's not clear to me how IE/Edge are behaving with respect to #2. -Ekr On Mon, Jan 4, 2016 at 10:14 AM, Daniel Holbert <dholb...@mozilla.com> wrote: > On 01/04/2016 09:47 AM, Eric Rescorla wrote: > > I believe that Chrome will be making a similar change at a similar time > > > > -Ekr > > In contrast, it looks like IE & Edge will continue accepting SHA1 certs > on the web for another full year, until 2017. [1][2] > > ~Daniel > > [1] > https://blogs.windows.com/msedgedev/2015/11/04/sha-1-deprecation-update/ > [2] > > https://support.comodo.com/index.php?/Default/Knowledgebase/Article/View/973/102/important-change-announcement---deprecation-of-sha-1 > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
