public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jason Zhan" <zhan.jason@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] link key PIN code authentication
Date: Fri, 21 Dec 2007 16:42:36 +0000	[thread overview]
Message-ID: <951351190712210842u78ca4a25y7815ebf2d4589096@mail.gmail.com> (raw)
In-Reply-To: <1198163598.8050.253.camel@aeonflux>


[-- Attachment #1.1: Type: text/plain, Size: 2713 bytes --]

Hi, Marcel

Thank you for your kindly reply.

I am starting to look at the D-bus framework and passkey-agent.c in
utils/daemon/.

One question regarding the bluetooth applet, maybe it's a little bit stupid.
But I really I can't figure it out by myself.

In my program, I prefer the user enter the passkey from the terminal rather
than from the applet window. I afraid I need to disable the bluetooth
applet, since it always automatically jump out a window when it finds
devices requesting pass key.

The figure 1 presented in "Security interface" shows the applet was built
upon the D-bus. Do I need to do some changes on gnome/applet? Or just modify
the passkey agent.

Please give me some hints on how to disable the applet during the
authentication.

Many thanks and Merry Christmas,
Jason



On 20/12/2007, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Jason,
>
> > Currently, I am working on a project to handle the pairing procedure.
> > The aim is quite simple.  If  the authentication is required by the
> > user, the program will detect whether the link key exists. If not, the
> > program will print out several lines in the terminal and ask the user
> > entering the PIN code.  The authentication will perform based on the
> > PIN code which the user provided and finally the new link key for this
> > connection will be passed to the host for future connections if the
> > authentication is successful.
> >
> > The bluez exploits the D-Bus to manage the pin code and link key.
> > Since my application is very simple, I don't think I need the D-Bus
> > framework.
>
> D-Bus is a really simple framework and not using D-Bus means you can
> also not use hcid. Which means you have to duplicate all the effort
> inside hcid. If you have that much free time, have fun. However you time
> could be spent more useful ;)
>
> > HCI can send the command to LM by hci_send_cmd() method, but I cannot
> > find the suitable methods which can read back the request from the
> > LM.
>
> You would have to open a raw HCI socket and read the HCI events. See the
> Bluetooth specification for details. Please don't expect me to get into
> details here. The hcid does all this and with the passkey agent
> interface you have a nice framework to solve your problem. Use it.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

[-- Attachment #1.2: Type: text/html, Size: 3408 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-12-21 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 10:46 [Bluez-devel] link key PIN code authentication Jason Zhan
2007-12-20 15:13 ` Marcel Holtmann
2007-12-21 16:42   ` Jason Zhan [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=951351190712210842u78ca4a25y7815ebf2d4589096@mail.gmail.com \
    --to=zhan.jason@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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