From: Marcel Holtmann <marcel@holtmann.org>
To: Daniel Wagner <wagi@monom.org>
Cc: linux-bluetooth@vger.kernel.org,
Daniel Wagner <daniel.wagner@bmw-carit.de>
Subject: Re: [RFC v0 2/3] Bluetooth: Use hci_conn_auth() instead of open coded version
Date: Wed, 04 Jan 2012 07:51:55 -0800 [thread overview]
Message-ID: <1325692315.6454.36.camel@aeonflux> (raw)
In-Reply-To: <1325689584-15121-3-git-send-email-wagi@monom.org>
Hi Daniel,
> Note this will also enable the encryption which will
> not happen in the open coded version.
>
> Signed-off-by: Daniel Wagner <daniel.wagner@bmw-carit.de>
> ---
> net/bluetooth/hci_event.c | 12 ++----------
> 1 files changed, 2 insertions(+), 10 deletions(-)
>
> diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c
> index d37f5b2..453e483 100644
> --- a/net/bluetooth/hci_event.c
> +++ b/net/bluetooth/hci_event.c
> @@ -1296,11 +1296,7 @@ static void hci_cs_remote_name_req(struct hci_dev *hdev, __u8 status)
> if (!hci_outgoing_auth_needed(hdev, conn))
> goto unlock;
>
> - if (!test_and_set_bit(HCI_CONN_AUTH_PEND, &conn->pend)) {
> - struct hci_cp_auth_requested cp;
> - cp.handle = __cpu_to_le16(conn->handle);
> - hci_send_cmd(hdev, HCI_OP_AUTH_REQUESTED, sizeof(cp), &cp);
> - }
> + hci_conn_auth(conn, BT_SECURITY_HIGH, conn->auth_type);
this is not a replacement. Not even a little bit. You are currently
messing with powers that can break qualification.
Regards
Marcel
next prev parent reply other threads:[~2012-01-04 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 15:06 [RFC v0 0/3] auth & enrypt cleanup attempt Daniel Wagner
2012-01-04 15:06 ` [RFC v0 1/3] Bluetooth: Make hci_conn_auth/encrypt public functions Daniel Wagner
2012-01-04 15:50 ` Marcel Holtmann
2012-01-04 15:06 ` [RFC v0 2/3] Bluetooth: Use hci_conn_auth() instead of open coded version Daniel Wagner
2012-01-04 15:51 ` Marcel Holtmann [this message]
2012-01-04 15:58 ` Daniel Wagner
2012-01-04 15:06 ` [RFC v0 3/3] Bluetooth: Use hci_conn_encrypt() " Daniel Wagner
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=1325692315.6454.36.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wagi@monom.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