Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: liang yu <iamyuliang@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Does OBEX authentication works in OPP?
Date: Wed, 17 Nov 2010 12:15:26 +0000	[thread overview]
Message-ID: <20101117121526.GA16972@jh-x301> (raw)
In-Reply-To: <AANLkTikTyH+3LLbr=ytu+9jcE8Sk_wTqdRyn9jwK821a@mail.gmail.com>

Hi,

On Wed, Nov 17, 2010, liang yu wrote:
> According to the Bluetooth SIG profile OBEX authentication is not used
> in OPP. But in source code of Obexd-0.36/plugins/opp.c, the function
> opp_chkput invokes manager_request_authorization. Does this mean that
> in your implementation it is still checked OBEX authentication in opp?
>     Doea anybody give me some tips.

The code you found (and as the function name also implies) is about
authorization and not authentication. So no, OBEX authentication is not
used with OPP.

Johan

  reply	other threads:[~2010-11-17 12:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17  3:43 Does OBEX authentication works in OPP? liang yu
2010-11-17 12:15 ` Johan Hedberg [this message]
2010-11-17 13:03   ` liang yu

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=20101117121526.GA16972@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=iamyuliang@gmail.com \
    --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