News for hackers. Stuff that matters.
Re:A DNS hijacking wave is targeting companies at an almost ... by bonyt on Friday January 11, 2019 @03:30PM (#18886663)
What ever happened to HPKP? It seems like that would somewhat mitigate these attacks since they rely on using their control over the domain to get a new DV cert. A pinned certificate would at least protect those who have accessed the sites before.
Re:A DNS hijacking wave is targeting companies at an almost ... by duskwuff on Friday January 11, 2019 @04:21PM (#18887175)
HPKP could have potentiated these attacks by allowing an attacker to pin their certificate while they were in control of the domain, making it difficult for the domain owner to ever fully regain control.
Re:A DNS hijacking wave is targeting companies at an almost ... by mh- on Friday January 11, 2019 @03:34PM (#18886699)
Re:A DNS hijacking wave is targeting companies at an almost ... by moosingin3space on Friday January 11, 2019 @03:51PM (#18886844)
If you're confused as to why, this article was illuminating: https://scotthelme.co.uk/using-security-features-to-do-bad-t...
Re:A DNS hijacking wave is targeting companies at an almost ... by tptacek on Friday January 11, 2019 @05:07PM (#18887641)
HPKP was underdesigned; it was a protocol evolution of something Google was already doing semi-manually. There was a competing initiative inside Google --- certificate transparency --- and that won out.

There's validity in the approach and I hope it comes back sometime, maybe with additional mechanism around managing pins.

Re:A DNS hijacking wave is targeting companies at an almost ... by dcbadacd on Saturday January 12, 2019 @10:15AM (#18891473)
Is HPKP Report Only also being deprecated?
Re:A DNS hijacking wave is targeting companies at an almost ... by ufmace on Friday January 11, 2019 @07:07PM (#18888460)
Being widely phased-out due to being too risky and error-prone. Attacks like this get a lot of media attention, but are pretty rare overall. It's much more common for someone to handle certificates and servers badly somehow, ending up in locking all of your visitors out of your own site, or you never bother with it, but the attacker who takes over your domain does, once again basically hijacking your domain name indefinitely.

I never set it up for any of my sites for the same reason, just too many ways for it to go wrong.