Skip to content

RFC nl80211 key handling improvements

Johannes Berg linux-wireless 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2nl80211: introduce new key attributesinclude/linux/nl80211.h net/wireless/nl80211.c+191 -470 replies
2/2cfg80211: rework key operationinclude/linux/nl80211.h include/net/cfg80211.h net/mac80211/ibss.c +14 more+553 -1610 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC 0/2] nl80211 key handling improvements

I dislike the current situation in nl80211, you cannot connect to any protected network without wpa_supplicant, but nl80211 can't _properly_ be used to set keys either...

These patches implement my new plan. According to that plan, static key configuration is passed directly to CONNECT or JOIN_IBSS along with the privacy flag, or the privacy flag itself is used to indicate that the application will later set the keys appropriately.

Internally, we store all the keys and call the add_key() function after we have joined the IBSS or connected to the AP (this could be changed if there are drivers that need static keys during connect(), but that seems rather unlikely). The only complication is shared key auth -- but this can be handled by simply passing the required WEP key directly to ->auth() or ->connect().

This might break iwm wrt. shared key auth if that currently works, but I couldn't figure out how it actually works now, if at all.

johannes