{"push_id":904871421,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"97fe888021b53c6372df36c1a427914e4afc2850","before":"d3b259e245ac256a9deb8fc4d49e2fa229b58566","commits":[{"sha":"97fe888021b53c6372df36c1a427914e4afc2850","author":{"email":"687de796550c0708cb6ea5602e58e2265b5a40b9","name":"sthen"},"message":"Remove \"C=US, O=VeriSign, Inc., OU=Class 3 Public Primary Certification\nAuthority\" (serial 3c:91:31:cb:1f:f6:d0:1b:0e:9a:b8:d0:44:bf:12:be) root\ncertificate from cert.pem. ok rpe@\n\nSymantec/VeriSign say \"Browsers/root store operators are encouraged to\nremove/untrust this root from their root stores\" and \"hasn't been used to\ngenerate new certificates in several years, and will now be repurposed to\nprovide transition support for some of our enterprise customers' legacy,\nnon-public applications\" (https://www.symantec.com/page.jsp?id=roots,\nhttp://www.scmagazine.com/google-will-remove-trust-of-symantecs-pca3-g1-certificate/article/459688/).\n\nAlso see\n\nhttps://knowledge.symantec.com/support/ssl-certificates-support/index?page=content&id=ALERT1941\nhttps://googleonlinesecurity.blogspot.co.uk/2015/12/proactive-measures-in-digital.html","distinct":true,"url":"https://api.github.com/repos/robertbachmann/openbsd-libcrypto/commits/97fe888021b53c6372df36c1a427914e4afc2850"}]}