News for hackers. Stuff that matters.
Re:How not to run a CA by codebeaker on Thursday March 01, 2018 @10:49AM (#16492885)
They're not verifying your identity, just that you control the hardware running the domain that you want to generate a certificate for.
Re:How not to run a CA by peterwwillis on Thursday March 01, 2018 @11:18AM (#16493217)
Correction: that you can control the IP space advertised to Let's Encrypt. A BGP exploit would result in getting valid certs for someone else's domain/host. It's almost trivial to exploit BGP, which is why PKI is so important... so it should actually be incredibly difficult to get a cert.
Re:How not to run a CA by discreditable on Thursday March 01, 2018 @11:55AM (#16493668)
If someone is hijacking BGP to MITM the world, how are the old methods any better?
Re:How not to run a CA by snuxoll on Thursday March 01, 2018 @12:20PM (#16493980)
If you could hijack BGP you could just as easily inject routes to intercept DNS requests as well.
Re:How not to run a CA by walrus01 on Thursday March 01, 2018 @02:32PM (#16495343)
This is why ISPs use tools like RPKI validation of received routes, and things like the ARIN, RADB and RIPE route-servers.
Re:How not to run a CA by icedchai on Thursday March 01, 2018 @04:47PM (#16496686)
Almost nobody uses RPKI: https://rpki-monitor.antd.nist.gov/