OpenBSD cvs log

created 2019-05-04T02:33:44Z
begin 2017-10-21T00:00:00Z
end 2017-10-22T00:00:00Z
path src/sys
commits 5

date 2017-10-21T06:11:22Z
author visa
files src/sys/arch/mips64/conf/files.mips64 log diff annotate
src/sys/arch/mips64/include/cpu.h log diff annotate
src/sys/arch/mips64/include/mplock.h log diff annotate
message Use MI mplock on mips64.

OK mpi@

date 2017-10-21T20:15:17Z
author patrick
files src/sys/net80211/ieee80211_output.c log diff annotate
src/sys/net80211/ieee80211_proto.h log diff annotate
message Make ieee80211_classify() available in a header so we can make the
priority visible to underlying bus protocols like bwfm(4)'s bcdc.

date 2017-10-21T20:19:37Z
author patrick
files src/sys/dev/usb/if_bwfm_usb.c log diff annotate
message Initialize all fields in the BCDC protocol, otherwise the controller
behaves erratically and drops packets on TX. Found the hard way by
Jared McNeill. While there, also set the priority field.

ok stsp@

date 2017-10-21T20:43:03Z
author patrick
files src/sys/dev/ic/bwfm.c log diff annotate
message 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@

date 2017-10-21T20:43:20Z
author patrick
files src/sys/dev/ic/bwfmreg.h log diff annotate
src/sys/dev/ic/bwfmvar.h log diff annotate
message 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@