[RFC 0/2] nl80211 key handling improvements

[Johannes Berg <johannes@sipsolutions.net>]

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