From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Subject: [RFC] key management in wireless
Date: Wed, 22 Nov 2006 09:59:23 +0100 [thread overview]
Message-ID: <1164185964.2751.2.camel@ux156> (raw)
Hey,
As I was reading through lwn I found the article on kernel key
management and wondered wtf I have been smoking that I forgot that I
wanted to use it in wireless :)
Is anyone familiar with with the key management interface and how it
should be used here? It seems that we probably want our own upcall
mechanism for requesting keys and should request them when encryption is
turned on.
johannes
reply other threads:[~2006-11-22 8:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1164185964.2751.2.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).