All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Vincent <simon.vincent@xsilon.com>
To: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>
Cc: "linux-wpan@vger.kernel.org" <linux-wpan@vger.kernel.org>
Subject: Re: 802.15.4 security
Date: Thu, 18 Jun 2015 11:12:19 +0100	[thread overview]
Message-ID: <55829983.3080608@xsilon.com> (raw)
In-Reply-To: <20150528110026.70a44e0d@zoidberg>

Hi Phoebe,

I am having some problems with the 802.15.4 security.

What kernel version/gitref did you last test the 802.15.4 security on?
What level of security are you using? (1-7)

I can then have a look what has changed since and try and debug the 
problems I am seeing.

I find if I set the security level to 1,2,3 I get a kernel panic 
whenever a packet is sent.
If I set the security level to 4 the packets sent are corrupt.
If I set the security level to 5-7 wireshark decodes the packets as MIC 
check failed.

Regards

Simon

On 28/05/15 10:00, Phoebe Buckheister wrote:
> Hi Simon,
>
> sorry for taking so long to reply. Unfortunately, there's currently no
> actual documentation for the crypto layer (and I probably won't come
> around to write any sometime soon), but I have built an application
> that works with llsec [1].
>
> The process to set up a crypto config for a network is rougly outlined
> in [2] and [3]. There are more options to the crypto layer than are used
> there, but the process is pretty much the same: you add a number of
> devices you want to securely communicate with, add the keys those
> devices will use to communicate, and then set the general parameters
> for llsec (like default llsec, enabling the crypto layer and such).
>
> Hope that helps a little,
> Phoebe
>
>
> [1]
> https://github.com/mysmartgrid/hexabus/blob/pb-crypto/hostsoftware/hxbnm
> [2]
> https://github.com/mysmartgrid/hexabus/blob/pb-crypto/hostsoftware/hxbnm/src/hxbnm.cpp#L160
> [3]
> https://github.com/mysmartgrid/hexabus/blob/pb-crypto/hostsoftware/hxbnm/src/hxbnm.cpp#L90
>
> On Thu, 21 May 2015 14:23:10 +0100
> Simon Vincent <simon.vincent@xsilon.com> wrote:
>
>> What is the status of the crypto-layer? I can see a lot of crypto
>> functionality in the mac layer but I can't work out how to setup the
>> keys and enable encryption/authentication. Will this be part of the
>> wpan-tools?
>>
>> - Simon
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wpan"
>> in the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2015-06-18 10:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 13:23 802.15.4 security Simon Vincent
2015-05-28  9:00 ` Phoebe Buckheister
2015-06-18 10:12   ` Simon Vincent [this message]
2015-06-18 11:13     ` Phoebe Buckheister
2015-06-18 11:40       ` Phoebe Buckheister
2015-06-18 11:43         ` Simon Vincent
2015-06-18 15:02         ` Simon Vincent
2015-06-18 15:32           ` Alexander Aring
2015-06-18 11:42       ` Simon Vincent
2015-06-18 11:44         ` 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=55829983.3080608@xsilon.com \
    --to=simon.vincent@xsilon.com \
    --cc=linux-wpan@vger.kernel.org \
    --cc=phoebe.buckheister@itwm.fraunhofer.de \
    /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.