News for hackers. Stuff that matters.
Re:Key Reinstallation Attacks – Breaking WPA2 by Forcing Non... by pixl97 on Monday October 16, 2017 @09:45AM (#15483111)
Too bad DNS doesn't fall under properly protected against local attacks.
Re:Key Reinstallation Attacks – Breaking WPA2 by Forcing Non... by pfg on Monday October 16, 2017 @09:56AM (#15483198)
Fortunately, SSL/TLS (with HSTS) does not depend on your local DNS resolver being secure.
Re:Key Reinstallation Attacks – Breaking WPA2 by Forcing Non... by Someone1234 on Monday October 16, 2017 @10:22AM (#15483361)
HSTS only works if you have visited the site before or it is hard coded (see Chrome and Google services for example).

Reality is that DNS remains and will continue to remain a giant hole in TLS.

Re:Key Reinstallation Attacks – Breaking WPA2 by Forcing Non... by pfg on Monday October 16, 2017 @10:43AM (#15483504)
All major browsers implement HSTS preloading, and getting added is quite simple. A very large percentage of your average internet user's traffic is covered by this.
Re:Key Reinstallation Attacks – Breaking WPA2 by Forcing Non... by pixl97 on Monday October 16, 2017 @10:49AM (#15483556)
Preloading is a problem waiting to happen. It works fine when only a small portion of the internet uses it. But when you have 2 GB preload file with a few billion entries things are not going to work so well.
Re:Key Reinstallation Attacks – Breaking WPA2 by Forcing Non... by pfg on Monday October 16, 2017 @12:25PM (#15484388)
The idea is to make HTTPS the default before that happens. In the meantime, you can fit a lot of domains into bloom filter-like data structures.
Re:Key Reinstallation Attacks – Breaking WPA2 by Forcing Non... by Piskvorrr on Monday October 16, 2017 @10:00AM (#15483225)
Fail-safe is indeed the preferred option here, yet the resulting Denial of Service is still unpleasant.