From: Don Zickus <dzickus@redhat.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: using d-bus api to set security level
Date: Thu, 15 Sep 2016 17:27:50 -0400 [thread overview]
Message-ID: <20160915212750.GP98438@redhat.com> (raw)
In-Reply-To: <CABBYNZLrgvqSDu-CPAWek02SOFAKLzKdg5pQdQfU+vw-hWgL1g@mail.gmail.com>
On Wed, Sep 14, 2016 at 07:52:11PM +0300, Luiz Augusto von Dentz wrote:
> Hi Don,
>
> On Wed, Sep 14, 2016 at 6:59 PM, Don Zickus <dzickus@redhat.com> wrote:
> > Hi,
> >
> > I am trying to find the equivalent of using gatttool's --sec-level when
> > writing a python script to connect to an LE device over the d-bus API.
> >
> > It seems like I have to set the Characteristic correctly. But I am missing
> > something obvious when looking through the doc/ api files.
> >
> > Can someone point me to the right spot? Thanks!
>
> You can call Device1.Pair if you want to authenticate, once the LTK is
> exchanged it will be used automatically in the next connections.
Hi Luiz,
Thanks for the response. I guess if the Pair() fails with Authentication
failure, that implies the device does not support it? I was playing with
this TI sensortag and wanted to double check how it was connecting.
So does the authentication get setup by the agent? And the Pair() to the
agent determines if the link will be encrypted?
Cheers,
Don
prev parent reply other threads:[~2016-09-15 21:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 15:59 using d-bus api to set security level Don Zickus
2016-09-14 16:52 ` Luiz Augusto von Dentz
2016-09-15 21:27 ` Don Zickus [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=20160915212750.GP98438@redhat.com \
--to=dzickus@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).