Linux bluetooth development
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
Cc: Johan Hedberg <johan.hedberg@gmail.com>, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3 7/7] Bluetooth: Add secure flag for mgmt_pin_code_req
Date: Thu, 28 Apr 2011 15:34:45 -0300	[thread overview]
Message-ID: <20110428183445.GB2302@joana> (raw)
In-Reply-To: <1303985279-3944-8-git-send-email-waldemar.rymarkiewicz@tieto.com>

Hi Waldemar,

* Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com> [2011-04-28 12:07:59 +0200]:

> Extend the mgmt_pin_code_request interface to require secure
> pin code (16 digit) for authentication.
> 
> This is a kernel part of the secure pin code requirement notification
> to user space agent.
> 
> Signed-off-by: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com>
> ---
>  include/net/bluetooth/hci_core.h |    2 +-
>  include/net/bluetooth/mgmt.h     |    1 +
>  net/bluetooth/hci_event.c        |    9 +++++++--
>  net/bluetooth/mgmt.c             |    3 ++-
>  4 files changed, 11 insertions(+), 4 deletions(-)

All patches but 5/7 were applied. thanks.

-- 
Gustavo F. Padovan
http://profusion.mobi

      reply	other threads:[~2011-04-28 18:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-28 10:07 [PATCH v3 0/7] Handle link key type and security requirements Waldemar Rymarkiewicz
2011-04-28 10:07 ` [PATCH v3 1/7] Bluetooth: Add definitions for link key types Waldemar Rymarkiewicz
2011-04-28 10:07 ` [PATCH v3 2/7] Bluetooth: Don't modify sec_level if auth failed Waldemar Rymarkiewicz
2011-04-28 10:07 ` [PATCH v3 3/7] Bluetooth: Map sec_level to link key requirements Waldemar Rymarkiewicz
2011-04-28 10:07 ` [PATCH v3 4/7] Bluetooth: Ignore key unauthenticated for high security Waldemar Rymarkiewicz
2011-04-28 10:07 ` [PATCH v3 5/7] Bluetooth: Double check sec req for pre 2.1 device Waldemar Rymarkiewicz
2011-04-28 18:09   ` Gustavo F. Padovan
2011-04-29  8:23     ` Waldemar.Rymarkiewicz
2011-04-28 18:11   ` Johan Hedberg
2011-04-28 21:08     ` Johan Hedberg
2011-04-29  8:30       ` Waldemar.Rymarkiewicz
2011-04-29  8:10     ` Waldemar.Rymarkiewicz
2011-04-28 10:07 ` [PATCH v3 6/7] Bluetooth: Respect local MITM req in io_cap reply Waldemar Rymarkiewicz
2011-04-28 10:07 ` [PATCH v3 7/7] Bluetooth: Add secure flag for mgmt_pin_code_req Waldemar Rymarkiewicz
2011-04-28 18:34   ` Gustavo F. Padovan [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=20110428183445.GB2302@joana \
    --to=padovan@profusion.mobi \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=waldemar.rymarkiewicz@tieto.com \
    /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