4 ms·
> Notice that stripe.ian.sh doesn't actually have an EV cert anymore: A system working as designed. Comodo has apologized for incorrectly revoking the certific
by owenmarshall 8y ago
> Notice that stripe.ian.sh doesn't actually have an EV cert anymore: A system working as designed.
Comodo has apologized for incorrectly revoking the certificate for stripe.ian.sh and offered a new EV cert.
https://www.comodoca.com/en-us/about/blog/on-comodo-ca’s-recent-revocation-of-an-ssl-certifi/ https://www.comodoca.com/en-us/about/blog/on-comodo-ca’s-rec...
In fact, many browser security developers would disagree with your assessment:
https://groups.google.com/forum/m/#!topic/mozilla.dev.security.policy/NjMmyA6MxN0 https://groups.google.com/forum/m/#!topic/mozilla.dev.securi...
- ocdtrekkie 8y agoI have very little faith in the opinions of "browser security developers" at the moment on account of browser security being a joke. Their focus has been on technical security but lacks practical security. Yes, stripe.ian.sh exists, but have you ever seen a truly malicious use of EV? Browser security developers concern themselves with arcane exploits of sandboxes while they don't mind nearly that every browser extension has full read/write access to everything people see and do. EV has flaws, but it's better than literally anything else. We shouldn't be promoting HTTPS if it isn't solving this, the other problems it attempts to solve are mostly overstated problems. Because phishing is a vastly bigger threat than MITM. EV has theoretical flaws but solves real problems, HTTPS without it has real problems and largely solves theoretical flaws.
- iancarroll 8y agoFrankly, I have yet to see a typical user point out EV as a problem solver. Usually, when I try to explain my work with EV to an average user, nobody knows what I'm talking about.
- ocdtrekkie 8y agoI would argue that's because the companies that should be using EV aren't, so users don't see EV often/enough. Google, Microsoft, etc. have no excuse to not be using, and emphasizing EV certificates. Consider how many "Microsoft support" scams would fall flat on their face if people were taught to look for the company they're dealing with was in a green box near the URL, and EV certs were shored up so that only major Fortune 500 or so companies were able to participate. And before someone suggests that users can't be taught this, there's precedent: We've been trying to teach users not to trust that "Secure" badge/lock icon they've gotten used to. The difference is, the secure icon never represented that they were communicating with someone trustworthy, but the EV designation would. EDIT: Also, hi Ian! stripe.ian.sh makes you a minor celebrity, and I'm honored by your presence. ;)
- dagenix 8y agoIts not Google's job to prop up CA vendor's business selling snake-oil certs. They don't see them as useful. There is compelling evidence that they aren't. So, Google is absolutely right not to encourage people to drop $2k+/year on Comodo for worthless certs and a "warranty" that means nothing.
- ocdtrekkie 8y agoBut pushing snake oil certs is exactly what they've been doing by forcing people to use HTTPS to avoid scare tactic "Not Secure" warnings. HTTPS is far less helpful than something like EV that includes identity, rather than an ethereal statement that you have an encrypted connection to "someone".
- dagenix 8y agoThe article makes a pretty compelling point that EV certs are worthless. Google and Apple seem to think that EV is worthless - that is why they are removing special treatment for them from their browsers. Many of the largest sites in the world that are the most appealing targets to phish have voted that they are worthless by not purchasing them. > forcing people to use HTTPS to avoid scare tactic "Not Secure" warnings. "Not Secure" is a literal description of the state of the connection. Its not secure. What should a browser say? I guess nothing because your site is so special that its users should be ok with having someone MITM the connection and inject who knows what into the page. Whether or not that is OK isn't your decision to make - its the right of your users to make that decision and saying "Not Secure" helps them. That you find that inconvenient for you is well ... inconvenient for _you_. > HTTPS is far less helpful than something like EV that includes identity The article makes a pretty compelling point that EV certs are worthless and do no better a job at providing security than regular certs.
- ocdtrekkie 8y agoI don't find the articles' arguments compelling at all, hence my statements contrary to it. Many of the arguments against EV, including in this article, are circular and depend on appeal to authority towards companies who don't like them.
- kelnos 8y ago> but have you ever seen a truly malicious use of EV? Assuming there hasn't been, I think this just supports the idea that EV certs aren't useful: the bad guys don't even feel the need to try to use them maliciously!
- ocdtrekkie 8y agoOr the return isn't worth it. Malicious actors have to assume that any given domain, certificate, URL, etc. will get blocked or shut down by the security industry, so being able to cycle those endpoints is key. EV is not easy to automate/cycle, and can also be more cost prohibitive, so each cycle is less profitable as well. That's my point: Systems that don't scale are less profitable to attempt to abuse for malicious ends, because more time and effort has to be invested into any given effort, and ideally, there are actual humans involved in the process which catch discrepancies. The other reason you may not see a lot of attempts to find exploits in EV (apart from Ian) is that most of the actors sites want to pretend to be aren't using EV either. If you want to fake yourself as Google, EV isn't going to help you since Google doesn't use it. I would argue the claim "bad actors aren't trying to abuse it so it isn't effective" to be silly, as that claim would apply among all methods that bad actors can't meaningfully abuse.