Re: About WPA2 compromised protocol

2017-10-17 Thread Stuart Henderson
On 2017-10-17, Nicolas Schmidt wrote: > Can this issue even be fixed on the AP side? For the APs that have received fixes, other than the problem with 11r, t seems they've mostly been on the client side (e.g. where an AP is also a client of another AP). It seems possible to detect attacks at the

Re: About WPA2 compromised protocol

2017-10-17 Thread Nicolas Schmidt
Can this issue even be fixed on the AP side? You could change the AP‘s behaviour to never ever resend Message 3, but that seems very drastic. As far as I understood the article by Vanhoef and Piessens, the vulnerability lies within the behavior of the client (that conforms to the 802.11i amendm

Re: About WPA2 compromised protocol

2017-10-17 Thread x9p
nice :) > Just for the fun: > http://www.commitstrip.com/en/2017/10/16/wpa2-vulnerability-just-a-small-update/ >

Re: About WPA2 compromised protocol

2017-10-17 Thread R0me0 ***
Stefan Sperling r0x :D Cheers 2017-10-17 15:19 GMT-02:00 Christoph R. Murauer : > The patch is there since 6.1 027 on the errata page. > > Saw the comic yesterday at Libertree. > > > On Tue, 17 Oct 2017 19:09:29 +0200 > > "Stephane HUC \"PengouinBSD\"" wrote: > > > >> Just for the fun: > >> ht

Re: About WPA2 compromised protocol

2017-10-17 Thread Christoph R. Murauer
The patch is there since 6.1 027 on the errata page. Saw the comic yesterday at Libertree. > On Tue, 17 Oct 2017 19:09:29 +0200 > "Stephane HUC \"PengouinBSD\"" wrote: > >> Just for the fun: >> http://www.commitstrip.com/en/2017/10/16/wpa2-vulnerability-just-a-small-update/ > > I saw somebody sh

Re: About WPA2 compromised protocol

2017-10-17 Thread Matthew Graybosch
On Tue, 17 Oct 2017 19:09:29 +0200 "Stephane HUC \"PengouinBSD\"" wrote: > Just for the fun: > http://www.commitstrip.com/en/2017/10/16/wpa2-vulnerability-just-a-small-update/ I saw somebody share that on Mastodon this morning. :) On a more serious note; am I correct in assuming that the patch

Re: About WPA2 compromised protocol

2017-10-17 Thread Stephane HUC "PengouinBSD"
Just for the fun: http://www.commitstrip.com/en/2017/10/16/wpa2-vulnerability-just-a-small-update/ Le 10/16/17 à 15:53, Lampshade a écrit : > Stefan Sperling: >> Also this was *NOT* a protocol bug. >> arstechnica claimed such nonesense without any basis in fact and >> now everybody keeps repeatin

Re: About WPA2 compromised protocol

2017-10-16 Thread Lampshade
Stefan Sperling: > Also this was *NOT* a protocol bug. > arstechnica claimed such nonesense without any basis in fact and > now everybody keeps repeating it :( Actually, the researcher claimed that are in the standard itself. https://www.krackattacks.com/ The weaknesses are in the Wi-Fi standard

Re: About WPA2 compromised protocol

2017-10-16 Thread Eric Johnson
Apparently, it has already been patched on OpenBSD. >From https://www.krackattacks.com/ When did you first notify vendors about the vulnerability? We sent out notifications to vendors whose products we tested ourselves around 14 July 2017. After communicating with these vendors, we realiz

Re: About WPA2 compromised protocol

2017-10-16 Thread Marc Espie
On Mon, Oct 16, 2017 at 12:58:45PM +0200, Stefan Sperling wrote: > On Mon, Oct 16, 2017 at 12:45:24PM +0200, Erik van Westen wrote: > > But did every manufacturer make the same mistake then? > > Yes. To sum up what I know: - WPA2 is still sound cryptographically; - there was no formal analysis of

Re: About WPA2 compromised protocol

2017-10-16 Thread Stefan Sperling
On Mon, Oct 16, 2017 at 06:47:21AM -0400, Raul Miller wrote: > What is the relevant language from the spec? Well, the spec is huge. The section on WPA is pretty long. Everyone can download the spec from IEEE. I am not going to quote it here.

Re: About WPA2 compromised protocol

2017-10-16 Thread Stefan Sperling
On Mon, Oct 16, 2017 at 12:45:24PM +0200, Erik van Westen wrote: > But did every manufacturer make the same mistake then? Yes.

Re: About WPA2 compromised protocol

2017-10-16 Thread Raul Miller
On Mon, Oct 16, 2017 at 6:43 AM, Stefan Sperling wrote: > On Mon, Oct 16, 2017 at 10:22:26AM +, C. L. Martinez wrote: >> Regarding WPA2 alert published today: https://www.krackattacks.com/, >> if I use an IPSec tunnel with shared-key or certifcate or an OpenVPN >> connection to authenticate a

Re: About WPA2 compromised protocol

2017-10-16 Thread Erik van Westen
Op 16-10-2017 om 12:43 schreef Stefan Sperling: > On Mon, Oct 16, 2017 at 10:22:26AM +, C. L. Martinez wrote: >> HI all, >> >> Regarding WPA2 alert published today: https://www.krackattacks.com/, >> if I use an IPSec tunnel with shared-key or certifcate or an OpenVPN >> connection to authentic

Re: About WPA2 compromised protocol

2017-10-16 Thread Stefan Sperling
On Mon, Oct 16, 2017 at 10:22:26AM +, C. L. Martinez wrote: > HI all, > > Regarding WPA2 alert published today: https://www.krackattacks.com/, > if I use an IPSec tunnel with shared-key or certifcate or an OpenVPN > connection to authenticate and protect clients and hostAP comms, is > this vu

Re: About WPA2 compromised protocol

2017-10-16 Thread Stefan Sperling
On Mon, Oct 16, 2017 at 10:22:26AM +, C. L. Martinez wrote: > is this vulnerability mitigated? Yes. This was 6.1 errata 027.

Re: About WPA2 compromised protocol

2017-10-16 Thread Erik van Westen
Op 16-10-2017 om 12:22 schreef C. L. Martinez: > HI all, > > Regarding WPA2 alert published today: https://www.krackattacks.com/, > if I use an IPSec tunnel with shared-key or certifcate or an OpenVPN > connection to authenticate and protect clients and hostAP comms, is > this vulnerability mitiga

About WPA2 compromised protocol

2017-10-16 Thread C. L. Martinez
HI all, Regarding WPA2 alert published today: https://www.krackattacks.com/, if I use an IPSec tunnel with shared-key or certifcate or an OpenVPN connection to authenticate and protect clients and hostAP comms, is this vulnerability mitigated? Thanks.