Google Chrome has announced that it will stop trusting public server certificates (SSL/TLS certificates) that support the client authentication extended key usage (clientAuth EKU) starting June 15, 2026.
This change won’t impact most users or websites (e.g., organizations that use SSL certificates for server authentication only). But if you’re using your SSL certificate for client authentication, you’ll need to make changes sooner rather than later.
But why is this change happening? And what does this removal of the clientAuth EKU from public SSL certificates mean for your organization?
Let’s hash it out.
The post Chrome: New SSL Certificates Can’t Support Client Authentication Starting June 15, 2026 appeared first on Hashed Out by The SSL Store™.
Unfortunately the string of phishing attacks using domain-confusionand legitimate-looking emails continues. This is the same…
SummaryI recently responded to an attack campaign where malicious actors injected code into GitHub Actions…
Internet security is leveling up with MPIC. While your organization likely won’t need to do…
Sept. 10: Get actionable insights from 20+ global experts as they discuss PQC readiness assessments,…
SummaryPyPI now checks for expired domains to prevent domain resurrection attacks,a type of supply-chain attack…
PyPI now serves project status markers in its standardindex APIs. This allows downstream consumers (like…
This website uses cookies.