News for hackers. Stuff that matters.
Re:Chrome's Plan to Distrust Symantec Certificates by nailer on Monday September 11, 2017 @07:15PM (#15223301)
Thanks James! Mike from CertSimple here. HN folk can give me a shout anytime ([email protected]) or ask here - it's midnight in the UK but I'll be back up in the morn!
Re:Chrome's Plan to Distrust Symantec Certificates by nodesocket on Monday September 11, 2017 @07:38PM (#15223458)
I believe that EV certificates cannot be wildcard certs, is this still true?
Re:Chrome's Plan to Distrust Symantec Certificates by nailer on Monday September 11, 2017 @08:01PM (#15223610)
Yep, what @detaro said. Here's the specifics: https://certsimple.com/blog/wildcard-ev-certificate
Re:Chrome's Plan to Distrust Symantec Certificates by darklajid on Tuesday September 12, 2017 @01:47AM (#15225079)
Like the site, but the example seems off.

It talks about 'bankofamerica.com.fraud.ru' in the first paragraph, but then discusses how 'fraud.ph' (why did we change TLDs? This should stick to ru or the above should be changed to ph) gets a wildcard cert for '* .com.fraud.com' (we changed TLDs again, to com this time. I assume we're talking about 'fraud.ph' getting a cert for * .com.fraud.ph - or .. we stick with ru)

Re:Chrome's Plan to Distrust Symantec Certificates by nailer on Tuesday September 12, 2017 @07:06AM (#15226312)
Good point - I was experiencing a bunch of fraud from the Phillippines and thought the Russian example was too cliched. I'll tweak the example to be more consistent.
Re:Chrome's Plan to Distrust Symantec Certificates by detaro on Monday September 11, 2017 @07:47PM (#15223516)
yes.