diff options
| author | sthen <> | 2015-12-15 20:23:51 +0000 |
|---|---|---|
| committer | sthen <> | 2015-12-15 20:23:51 +0000 |
| commit | 5fb069e3ba55af146badaa0793c0d70bdde639ab (patch) | |
| tree | 1bc02fc62f67c5d56dc57729d2ff39f4080a0f13 /src/lib/libc/stdlib | |
| parent | c5249151abeb246faa9d2abd4f8cce971592ac97 (diff) | |
| download | openbsd-5fb069e3ba55af146badaa0793c0d70bdde639ab.tar.gz openbsd-5fb069e3ba55af146badaa0793c0d70bdde639ab.tar.bz2 openbsd-5fb069e3ba55af146badaa0793c0d70bdde639ab.zip | |
Remove "C=US, O=VeriSign, Inc., OU=Class 3 Public Primary Certification
Authority" (serial 3c:91:31:cb:1f:f6:d0:1b:0e:9a:b8:d0:44:bf:12:be) root
certificate from cert.pem. ok rpe@
Symantec/VeriSign say "Browsers/root store operators are encouraged to
remove/untrust this root from their root stores" and "hasn't been used to
generate new certificates in several years, and will now be repurposed to
provide transition support for some of our enterprise customers' legacy,
non-public applications" (https://www.symantec.com/page.jsp?id=roots,
http://www.scmagazine.com/google-will-remove-trust-of-symantecs-pca3-g1-certificate/article/459688/).
Also see
https://knowledge.symantec.com/support/ssl-certificates-support/index?page=content&id=ALERT1941
https://googleonlinesecurity.blogspot.co.uk/2015/12/proactive-measures-in-digital.html
Diffstat (limited to 'src/lib/libc/stdlib')
0 files changed, 0 insertions, 0 deletions