All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Scott James Remnant <keybuk@chromium.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] agent: allow agent to reply to RequestPinCode with bytes
Date: Sat, 14 Jan 2012 17:41:47 +0100	[thread overview]
Message-ID: <1326559307.6454.270.camel@aeonflux> (raw)
In-Reply-To: <1326505957-27555-3-git-send-email-keybuk@chromium.org>

Hi Scott,

> Since the specification allows the PIN to be a sequence of arbitrary
> octets, and not a UTF-8 string, allow the userspace agent to reply
> with such a sequence (as a D-Bus Array of Bytes).
> 
> This means a userspace agent can deal with devices that require their
> BD_ADDR (or the host's) as a PIN, and take care of trying multiple of
> such requirements.

this has been discussed before and the answer is a clear no to this.

You can however write a plugin that can handle binary PIN codes.

Regards

Marcel



  reply	other threads:[~2012-01-14 16:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-14  1:52 [PATCH 1/2] Pass length of PIN through callbacks Scott James Remnant
2012-01-14  1:52 ` [PATCH 2/2] agent: allow agent to reply to RequestPinCode with bytes Scott James Remnant
2012-01-14 16:41   ` Marcel Holtmann [this message]
2012-01-14 20:32     ` Scott James Remnant
2012-01-14 20:34     ` Scott James Remnant
2012-01-16 15:44       ` David Herrmann
2012-01-17  6:23         ` Scott James Remnant
2012-01-17  7:47           ` Marcel Holtmann
2012-01-17  8:30             ` Scott James Remnant
2012-01-17 10:23               ` Marcel Holtmann
2012-01-17 17:57                 ` Scott James Remnant

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=1326559307.6454.270.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=keybuk@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.