diff options
| author |   patrick <patrick@openbsd.org> | 2017-10-21 20:43:03 +0000 |
|---|---|---|
| committer | patrick <patrick@openbsd.org> | 2017-10-21 20:43:03 +0000 |
| commit | 63498aa87cbe8e5ed9cdbbb7cc4275894563b8e1 (patch) | |
| tree | da6c110bee88c42a5f3612165396129cd61ca6e5 /usr.bin/ssh/readconf.c | |
| parent | Initialize all fields in the BCDC protocol, otherwise the controller (diff) | |
| download | wireguard-openbsd-63498aa87cbe8e5ed9cdbbb7cc4275894563b8e1.tar.xz wireguard-openbsd-63498aa87cbe8e5ed9cdbbb7cc4275894563b8e1.zip | |
Even though letting the firmware handle the handshake is nice from
a user perspective, it's rather horrible from a security perspective.
Especially since there has not only been the KRACK attack, but also
exploited wireless firmware. Thus this commit changes the way that
bwfm(4) is integrated into our network stack. Instead of making it
an Ethernet controller with some WiFi capability, deeply integrate
it into the net80211 stack. This way we can do the WPA handshake in
software and we don't have to reimplement or copy too much code from
the net80211 stack. Some code taken from NetBSD where Jared McNeill
committed bwfm(4) with net80211 integration as well.
Discussed with and "looks good" stsp@
Diffstat (limited to 'usr.bin/ssh/readconf.c')
0 files changed, 0 insertions, 0 deletions