From: Anderson Lizardo <anderson.lizardo@openbossa.org>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 0/3] Basic attribute permission support
Date: Wed, 1 Dec 2010 12:13:03 -0400 [thread overview]
Message-ID: <1291219986-29913-1-git-send-email-anderson.lizardo@openbossa.org> (raw)
Hi,
This patchset adds initial support for attribute permission checks. Currently,
only access and authentication permissions are checked. Authorization
permissions require integration with the BlueZ agent, which is not implemented
yet.
There are some pending issues necessary for a minimum complete attribute
permission support (all of them are being worked on):
* The attribute client, upon receiving the "Insufficient Encryption" error,
shall increase the security level and resend the failed request.
* The attribute server shall verify the connection permissions on each ATT
request, and not just once on connection callback.
* On kernel side, increasing the security level (using setsockopt()) shall
trigger SMP negotiation for a LE connection, blocking next socket I/O until
negotiation is finished.
* On BR/EDR, link encryption needs to be done "on the fly" before resending the
failed ATT request.
Albeit the above issues, we believe these patches are ready for commit.
Regards,
--
Anderson Lizardo
OpenBossa Labs - INdT
Manaus - Brazil
next reply other threads:[~2010-12-01 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 16:13 Anderson Lizardo [this message]
2010-12-01 16:13 ` [PATCH 1/3] Initial attribute permission implementation Anderson Lizardo
2010-12-02 10:10 ` Johan Hedberg
2010-12-02 13:33 ` Anderson Lizardo
2010-12-02 14:58 ` Johan Hedberg
2010-12-01 16:13 ` [PATCH 2/3] Check attribute permissions in attribute server Anderson Lizardo
2010-12-01 16:13 ` [PATCH 3/3] Check authentication permissions on " Anderson Lizardo
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=1291219986-29913-1-git-send-email-anderson.lizardo@openbossa.org \
--to=anderson.lizardo@openbossa.org \
--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 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).