From: Marcel Holtmann <marcel@holtmann.org>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org, johan.hedberg@gmail.com
Subject: Re: [RFC 2/2] Bluetooth: Add support for returning the encryption key size
Date: Fri, 15 Apr 2011 22:24:25 -0700 [thread overview]
Message-ID: <1302931465.2503.33.camel@aeonflux> (raw)
In-Reply-To: <1302915440.2503.26.camel@aeonflux>
Hi Vinicius,
> And of course the same now applies for PIN code length. Even if with
> Simple Pairing this does not matter anymore. For Legacy Pairing this is
> still relevant.
forget about this comment. It is actually bogus since the HIGH vs MEDIUM
security for Legacy Pairing implies the PIN length requirement already.
We just need to make sure to enforce it properly via the new in-kernel
handling of pairing.
Regards
Marcel
prev parent reply other threads:[~2011-04-16 5:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 0:04 [RFC 0/2] Returning Encryption Key Size Vinicius Costa Gomes
2011-04-15 0:04 ` [RFC 1/2] Bluetooth: Add support for storing the key size Vinicius Costa Gomes
2011-04-15 0:04 ` [RFC 2/2] Bluetooth: Add support for returning the encryption " Vinicius Costa Gomes
2011-04-16 0:57 ` Marcel Holtmann
2011-04-16 5:24 ` Marcel Holtmann [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=1302931465.2503.33.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=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