From: Dave Higton <davehigton@dsl.pipex.com>
To: linux-bluetooth@vger.kernel.org
Subject: RE: Bluetooth encryption algorithms
Date: Fri, 19 Aug 2011 22:13:36 +0100 [thread overview]
Message-ID: <2a72630552.davehigton@dsl.pipex.com> (raw)
In-Reply-To: <5B4B9A479BF6994B88EA975675EC5B790580AC7068@MES1OS2SXC003.mes1.tconet.net>
In message <5B4B9A479BF6994B88EA975675EC5B790580AC7068@MES1OS2SXC003.mes1.tconet.net>
"Cufi, Carles" <carles.cufi@nordicsemi.no> wrote:
> Hi there,
> > So if anyone can point me to sources of information detailed and
> > explicit enough to show me how Bluetooth encryption and decryption are
> > done, I would very much appreciate it. I have the Bluetooth core
> > specification, but I'm not confident that I can implement correctly from
> > it alone. I'm also looking for test data, ideally for each step through
> > each algorithm.
>
> Just register with bluetooth.org and get the Core Spec v4.0. All the
> information you need is there.
>
> https://www.bluetooth.org/Technical/Specifications/adopted.htm
Like I said in the bit you quoted, I have the specification (I have
Core Spec v4.0, although I didn't specifically say that). At least
I have, since I first posted, found the test data - I was almost sure
I'd seen them before, but I couldn't find them via the index. I saw
them by accident when browsing for something else. (Encryption test
data not in the Security section... who'd have thought it?)
I'm still hoping for something more tutorial or explanatory, but if
I can't find anything, at least the test data will give me more
confidence to try implementing from the specification.
Dave
next prev parent reply other threads:[~2011-08-19 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-10 15:41 Bluetooth encryption algorithms dave higton
2011-08-15 12:54 ` Cufi, Carles
2011-08-19 21:13 ` Dave Higton [this message]
2011-08-21 21:13 ` Ash K
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=2a72630552.davehigton@dsl.pipex.com \
--to=davehigton@dsl.pipex.com \
--cc=linux-bluetooth@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 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.