News for hackers. Stuff that matters.
Re:Hijack of Amazon’s domain service used to reroute web tra... by Kalium on Tuesday April 24, 2018 @03:14PM (#16915665)
> * Pick a preferred SSL issuer and stick with them. Add a CAA DNS record only allowing that one issuer.

It may be worth also suggesting HPKP here. That would be effective for many customers.

> * DNSSEC? Make sure to choose an SSL issuer that will correctly test DNSSEC?

This basically means you can't use Route53, which is a deal-breaker for a lot of people running services.

Re:Hijack of Amazon’s domain service used to reroute web tra... by blibble on Tuesday April 24, 2018 @03:47PM (#16915935)
GCP supports DNSSEC, I moved all my domains away from Amazon due to this

was very easy to setup on GCP too

Re:Hijack of Amazon’s domain service used to reroute web tra... by ryao on Tuesday April 24, 2018 @07:34PM (#16917594)
Use cloudflare. Unlike Amazon, their DNS is free and it is supposed to be among the fastest.

Then again, DNSSEC is useless against a BGP hijack where the nameservers for the domain are replaced with malicious ones.

Re:Hijack of Amazon’s domain service used to reroute web tra... by Kalium on Wednesday April 25, 2018 @12:43PM (#16923344)
Believe me, I'd very much like that. I'm better aware than most of their technical capabilities and speed.

When I say "a lot of people running services", I don't mean me. I mean a lot of people I know and associate with. A lot of them have grown to rely on close integration between DNS and all their other infrastructure services. That CF covers them technically isn't helpful - they expected it all under one roof and they need to not spend cycles on thinking about something marginal to them like DNS.

One of the biggest selling-points of AWS is that it puts all your services in one spot. It limits orchestration work and makes life simpler. Asking people to leave that for security improvements may be necessary, but it's not a small ask.

Re:Hijack of Amazon’s domain service used to reroute web tra... by web007 on Tuesday April 24, 2018 @04:44PM (#16916393)
I thought HPKP was essentially deprecated - too many footgun scenarios and not enough specificity on "what to pin" since CAs can use / issue with multiple intermediates.
Re:Hijack of Amazon’s domain service used to reroute web tra... by Kalium on Tuesday April 24, 2018 @06:34PM (#16917250)
There are definitely a series of foot-gun-y scenarios with HPKP, just as with full DNSSEC. It's just one of the few things I can think of that gives you the ability to detect when a cert has changed unexpectedly.