From: Marcel Holtmann <marcel@holtmann.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Bluetooth fixes for 2.6.27
Date: Mon, 08 Sep 2008 23:53:57 +0200 [thread overview]
Message-ID: <1220910837.11655.28.camel@californication> (raw)
Hi Dave,
I do have three additional fixes for the Bluetooth subsystem that should
go into the 2.6.27 release. After the heated discussion, I really wanted
not to bother you until the next merge window, but from my perspective
all three patches fall in the regression or security fix category. That
is my personal view on these and feel free to disagree.
The first patch is a clear regression that got introduced with
2.6.27-rc1 when adding Simple Pairing support. I forgot to decrease the
reference count on an incoming ACL link. This patch actually makes the
code simpler.
The second patch fixes the authentication requirements. We do have to
separate between service discovery and actual profile channels. This is
a clear requirement of the Bluetooth Security Mode 4 introduced with the
addition of the Simple Pairing support. Not fixing this will result in
broken behavior when doing service discovery with Simple Pairing enabled
devices.
The third patch rejects insecure incoming connections. This is a clear
security issues since we can't rely on the initiator doing the right
thing and establishing an encrypted link. Malicious devices would just
skip that step and in that case we have to reject connection attempt
without going into the connection phase at all.
I tried to put detailed information into the commit messages to make it
clear why I submitted these patches in the -rc phase.
We do have one suspend/resume regression with the btusb driver that I
like to see fixed, but the fix would require new USB core functionality.
I am not sure if that happens in the 2.6.27 timeframe. I will check with
Oliver if we can come up with a patch that works with the current
kernel.
Regards
Marcel
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git master
This will update the following files:
include/net/bluetooth/hci_core.h | 3 ++-
net/bluetooth/af_bluetooth.c | 2 +-
net/bluetooth/hci_conn.c | 21 ++++++++++++++++++---
net/bluetooth/hci_event.c | 11 ++++-------
net/bluetooth/l2cap.c | 34 ++++++++++++++++++++++++++++------
net/bluetooth/sco.c | 2 +-
6 files changed, 54 insertions(+), 19 deletions(-)
through these ChangeSets:
Marcel Holtmann (3):
[Bluetooth] Fix reference counting during ACL config stage
[Bluetooth] Enforce correct authentication requirements
[Bluetooth] Reject L2CAP connections on an insecure ACL link
next reply other threads:[~2008-09-08 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 21:53 Marcel Holtmann [this message]
2008-09-09 0:05 ` Bluetooth fixes for 2.6.27 David Miller
2008-09-09 2:04 ` Marcel Holtmann
2008-09-09 2:42 ` David Miller
2008-09-09 4:28 ` Marcel Holtmann
2008-09-09 4:30 ` David Miller
2008-09-09 4:46 ` Marcel Holtmann
2008-09-09 4:48 ` David Miller
2008-09-09 6:08 ` Marcel Holtmann
2008-09-09 10:02 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 8:23 Marcel Holtmann
2008-08-19 8:38 ` David Miller
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=1220910837.11655.28.camel@californication \
--to=marcel@holtmann.org \
--cc=davem@davemloft.net \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox