News for hackers. Stuff that matters.
Re:Chrome's Plan to Distrust Symantec Certificates by hannob on Monday September 11, 2017 @06:06PM (#15222859)
> LetsEncrypt is wonderful, but if I'm a company that needs to show the company name next to the padlock, who should I be using?

Sorry, what's a company that needs to show the company name beside the padlock? (Except maybe: Company that has too much money to spend on pointless "premium" security services without any shown benefit.)

Re:Chrome's Plan to Distrust Symantec Certificates by samtho on Monday September 11, 2017 @06:13PM (#15222900)
EV is an option for companies that worry about branding - specifically ones that are well-known to do business offline. This extra layer of trust, relayed to the user from the web browser, reinforces the fact that they are on the correct website.

For example, I can go grab something like "bannk.com" (notice two 'n's) and get a DV cert for it - because I hypothetically own that name. Now, I can copy the real "bank.com" onto the site and perform a phishing attack. They both appear to be encrypted but the EV'd one has the organization noted, the fake one will not be able to have that legitimacy.

I am not saying the system isn't without its faults (people might not even notice), but it's an extra measure a company can do to keep itself distinguished from phshing websites or copycat services.

Re:Chrome's Plan to Distrust Symantec Certificates by mnx on Monday September 11, 2017 @07:04PM (#15223237)
Too many negatives in that last sentence.
Re:Chrome's Plan to Distrust Symantec Certificates by Normal_gaussian on Monday September 11, 2017 @06:14PM (#15222907)
> without any shown benefit

on the contrary, I know that the presence of an EV line has helped my mother avoid a pretty decent phishing attempt. Any company holding confidential details or data should have one, its just a shame they are so expensive (which due to their verification is unlikely to come down too far).