From: Marcel Holtmann <marcel@holtmann.org>
To: "Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: Allow L2CAP to increase the security level
Date: Tue, 08 Nov 2011 08:59:15 +0900 [thread overview]
Message-ID: <1320710358.15441.312.camel@aeonflux> (raw)
In-Reply-To: <1320677128-25949-2-git-send-email-padovan@profusion.mobi>
Hi Gustavo,
> Some incomming connections needs to increase the security level by
> requesting encryption for example (HID keyboard case). This change allows
> the userspace to change it through setsockopt with defer_setup enabled.
>
> Signed-off-by: Gustavo F. Padovan <padovan@profusion.mobi>
> ---
> include/net/bluetooth/l2cap.h | 1 +
> net/bluetooth/l2cap_core.c | 2 +-
> net/bluetooth/l2cap_sock.c | 13 ++++++++++---
> 3 files changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/include/net/bluetooth/l2cap.h b/include/net/bluetooth/l2cap.h
> index fdb2b78..5ff38e9 100644
> --- a/include/net/bluetooth/l2cap.h
> +++ b/include/net/bluetooth/l2cap.h
> @@ -810,5 +810,6 @@ int l2cap_chan_connect(struct l2cap_chan *chan);
> int l2cap_chan_send(struct l2cap_chan *chan, struct msghdr *msg, size_t len,
> u32 priority);
> void l2cap_chan_busy(struct l2cap_chan *chan, int busy);
> +int l2cap_chan_check_security(struct l2cap_chan *chan);
>
> #endif /* __L2CAP_H */
> diff --git a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
> index 793971c..6a5c1b2 100644
> --- a/net/bluetooth/l2cap_core.c
> +++ b/net/bluetooth/l2cap_core.c
> @@ -516,7 +516,7 @@ static inline u8 l2cap_get_auth_type(struct l2cap_chan *chan)
> }
>
> /* Service level security */
> -static inline int l2cap_chan_check_security(struct l2cap_chan *chan)
> +int l2cap_chan_check_security(struct l2cap_chan *chan)
> {
> struct l2cap_conn *conn = chan->conn;
> __u8 auth_type;
> diff --git a/net/bluetooth/l2cap_sock.c b/net/bluetooth/l2cap_sock.c
> index 664762e..b58f40c 100644
> --- a/net/bluetooth/l2cap_sock.c
> +++ b/net/bluetooth/l2cap_sock.c
> @@ -623,8 +623,12 @@ static int l2cap_sock_setsockopt(struct socket *sock, int level, int optname, ch
>
> chan->sec_level = sec.level;
>
> + if (!chan->conn)
> + break;
> +
> conn = chan->conn;
is this fixing a real bug? Can chan->conn really be NULL?
> - if (conn && chan->scid == L2CAP_CID_LE_DATA) {
> +
> + if (chan->scid == L2CAP_CID_LE_DATA) {
> if (!conn->hcon->out) {
> err = -EINVAL;
> break;
> @@ -632,9 +636,12 @@ static int l2cap_sock_setsockopt(struct socket *sock, int level, int optname, ch
>
> if (smp_conn_security(conn, sec.level))
> break;
> -
> - err = 0;
> sk->sk_state = BT_CONFIG;
> + } else if (sk->sk_state == BT_CONNECT2 &&
> + bt_sk(sk)->defer_setup) {
> + err = l2cap_chan_check_security(chan);
> + } else {
> + err = -EINVAL;
> }
> break;
>
You might wanna add some comments here on what each if block is for.
This becomes a complex statements and we need comments here to keep us
sane.
Regards
Marcel
next prev parent reply other threads:[~2011-11-07 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 14:45 [PATCH 1/2] Bluetooth: Rename l2cap_check_security() Gustavo F. Padovan
2011-11-07 14:45 ` [PATCH 2/2] Bluetooth: Allow L2CAP to increase the security level Gustavo F. Padovan
2011-11-07 23:59 ` Marcel Holtmann [this message]
2011-11-08 18:26 ` Gustavo Padovan
2011-11-07 23:56 ` [PATCH 1/2] Bluetooth: Rename l2cap_check_security() Marcel Holtmann
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=1320710358.15441.312.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).