@Obsolesce said in Why Let’s Encrypt is a really, really, really bad idea…:
@scottalanmiller said in Why Let’s Encrypt is a really, really, really bad idea…:
@Obsolesce said in Why Let’s Encrypt is a really, really, really bad idea…:
@scottalanmiller said in Why Let’s Encrypt is a really, really, really bad idea…:
@ingmarkoecher said in Why Let’s Encrypt is a really, really, really bad idea…:
@stacksofplates Yes, but it's also about preventing imposters - so you know that who you're talking to is who they claim they are.
This is true.... only so far as preventing a man in the middle attack. It doesn't tell you that you selected the right person in the first place, which is how people will read that.
Not really. I can create a cert that says I'm [email protected] or an ssl cert for my server that says facebook.com. A browser may not trust it by default because it comes from my own CA, but that's besides the point.
No one is discussing your own CA though. The CA mechanism is based on trusted roots.
I responded to certs specifically, regardless of context.
And you are correct, in that context. But that's not what context we were thinking of.