From: Johan Hedberg <johan.hedberg@gmail.com>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v3 1/6] lib: Add Key Size information to the security information
Date: Tue, 24 Jan 2012 16:21:05 +0200 [thread overview]
Message-ID: <20120124142105.GA1307@x220> (raw)
In-Reply-To: <1327413443-26375-1-git-send-email-vinicius.gomes@openbossa.org>
Hi Vinicius,
On Tue, Jan 24, 2012, Vinicius Costa Gomes wrote:
> Since some time the kernel has the capability to return the length of
> the key that was used to encrypt the link.
>
> This patch exposes that field to userspace so more applications can take
> decisions based on this information.
> ---
> lib/bluetooth.h | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
All six patches have been applied. Thanks.
Johan
prev parent reply other threads:[~2012-01-24 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 13:57 [PATCH BlueZ v3 1/6] lib: Add Key Size information to the security information Vinicius Costa Gomes
2012-01-24 13:57 ` [PATCH BlueZ v3 2/6] btio: Add support for getting the Encryption Key Size via btio Vinicius Costa Gomes
2012-01-24 13:57 ` [PATCH BlueZ v3 3/6] test: Add support for passing the CID to btiotest Vinicius Costa Gomes
2012-01-24 13:57 ` [PATCH BlueZ v3 4/6] test: Add support for btiotest to returning the key size Vinicius Costa Gomes
2012-01-24 13:57 ` [PATCH BlueZ v3 5/6] btio: Remove the default security level from btio Vinicius Costa Gomes
2012-01-24 13:57 ` [PATCH BlueZ v3 6/6] btio: Fix users to not expect a default security level Vinicius Costa Gomes
2012-01-24 14:21 ` Johan Hedberg [this message]
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=20120124142105.GA1307@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vinicius.gomes@openbossa.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).