Forum Discussion
Eric_E
Nov 16, 2022Iron Contributor
Dev Channel update to 109.0.1495.2 is live
Edit: I added Fixed unable to open local files when an instance of the browser is already running under changed behavior and updated the post to reflect the new build number.
Hello Insiders! To...
AndresPae
Jan 27, 2023Brass Contributor
This move to block using OS cert store in Edge starting 111 is really weird. In Enterpises there is very common that we have internal PKI. We can distribute those CA certs via AD GPO, via Intune CSP , - in such case certs are PUT to OS certstore. Even Mozilla Firefox got finally ability to use Windows store(and we are using this option). And now - dear MS - Edge not able to use Windows store? Do we understand it wrongly? https://learn.microsoft.com/en-us/deployedge/microsoft-edge-security-cert-verification.
As i understand 111 should launch in mid feb 2023 - this is almost soon.
As i understand 111 should launch in mid feb 2023 - this is almost soon.
Gunnar-Haslinger
Jan 27, 2023Iron Contributor
AndresPae yes, I think you understand it wrong.
And I think the article is written misleading.
There is this small sentence which should get your attention:
In addition to trusting the built-in roots that ship with Microsoft Edge, the browser will also query the underlying platform for—and trust—locally installed roots that users and/or enterprises installed.
so in fact nothing seems to change for Enterprise-CAs deployed to Windows-OS-CertStore.
See this Blog-Post here, which is written much clearer than the official documentation:
https://textslashplain.com/2022/12/06/tls-certificate-verification-changes-in-edge/
This blog is written by https://twitter.com/ericlaw who is working at MSFT/Edge
- AndresPaeJan 27, 2023Brass ContributorI read this small sentence several times forth and back and was even more confused. But - thanks - Your link explains it indeed much better than official page.