From: Stefan Schmidt <stefan@osg.samsung.com>
To: Simon Vincent <simon.vincent@xsilon.com>,
Alexander Aring <alex.aring@gmail.com>,
linux-wpan@vger.kernel.org
Subject: Re: The 802.15.4 Security Layer
Date: Thu, 18 Jun 2015 21:43:04 +0200 [thread overview]
Message-ID: <55831F48.4090905@osg.samsung.com> (raw)
In-Reply-To: <5582EAAD.1090605@xsilon.com>
Hello.
On 18/06/15 17:58, Simon Vincent wrote:
> Hi,
>
> On 18/06/15 16:42, Stefan Schmidt wrote:
>> Hello.
>>
>> On 18/06/15 14:31, Alexander Aring wrote:
>>> Hi all,
>>>
>>> I saw the latest discussion about the security layer and wants to
>>> open a
>>> new thread about discussion for access this layer over nl802154 and
>>> putting a "very easy to use" functionality into iwpan.
>>>
>>> I need to admit, I never tested myself this layer, also I told many
>>> times that the step to put security layer functionality into
>>> nl802154 is
>>> a necessary step. For that reason I declare the security layer as
>>> broken.
>>>
>>> Several months ago I started to put these functionality into wpan-tools
>>> and nl802154. It's just parsing a file at the moment and putting the
>>> all
>>> relevant entries for key, device, seclevel tables in cfg802154. Nothing
>>> more. These tables are handled like an ACL in 802.15.4 (so far I know)
>>> and necessary to do the "key lookup" procedure, on receiving decrypted
>>> frames.
>>>
>>> At weekend I will try to provide my stuff which I already have done and
>>> will try to explain what the idea for the next necessary steps are.
>>> It's
>>> just to start a discussion "How do deal with accessing llsec over
>>> nl802154/cfg802154".
>>>
>>> After we can accessing the sec layer over nl802154, we can hopefully
>>> remove
>>> the old interface stuff.
>>>
>>> Does this sounds like a plan?
>>
>> I think this is a good idea and I would gladly gve this some testing
>> next week. I bet Simon would do as well as he is currently looking
>> into it.
> Yes it would nice to tidy this all up and get a stable interface. I
> currently have some time to look at this and do some testing.
You have by any chance some small example code you used for testing the
llc stuff? It would be handy to start with something small and easy.
regards
Stefan Schmidt
next prev parent reply other threads:[~2015-06-18 19:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 12:31 The 802.15.4 Security Layer Alexander Aring
2015-06-18 15:42 ` Stefan Schmidt
2015-06-18 15:58 ` Simon Vincent
2015-06-18 19:43 ` Stefan Schmidt [this message]
2015-06-23 15:34 ` Simon Vincent
2015-06-23 16:00 ` Simon Vincent
2015-06-24 10:00 ` Alexander Aring
2015-06-24 14:01 ` Alexander Aring
2015-06-26 8:56 ` Simon Vincent
2015-06-26 9:32 ` Alexander Aring
2015-06-26 9:45 ` Stefan Schmidt
2015-06-26 9:58 ` Alexander Aring
2015-06-26 10:14 ` Stefan Schmidt
2015-06-26 10:24 ` Alexander Aring
2015-06-26 11:20 ` Alexander Aring
2015-06-21 21:12 ` Alexander Aring
2015-06-22 12:33 ` Phoebe Buckheister
2015-06-23 11:03 ` Alexander Aring
2015-06-23 12:46 ` Phoebe Buckheister
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=55831F48.4090905@osg.samsung.com \
--to=stefan@osg.samsung.com \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=simon.vincent@xsilon.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.