Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] pand seem to ignore any pin configurations
Date: Sun, 08 May 2005 00:02:47 +0200	[thread overview]
Message-ID: <1115503367.9031.31.camel@pegasus> (raw)
In-Reply-To: <200505072339.13643.rdorsch@web.de>

Hi Rainer,

> thanks for the quick reply. Where would I specify the PIN on the PANU? Should 
> pin_helper in hcid.conf provide this? Where would I specify the PIN on the 
> NAP?

if you use "security user" then the PIN is provided through the PIN
helper script.

> There is no --auth for pand:

You read my answer, do you? I said that I realized that it is missing
and that you should use --encrypt instead. It is fixed in the CVS.

> Do I need 
> 
>         # Authentication and Encryption (Security Mode 3)
>         auth enable;
>         encrypt enable;
> 
> in the device section of /etc/bluetooth/hcid.conf?

If you know what security mode 3 means, feel free to use it otherwise
you might wanna look into the Bluetooth specification first. And btw
there is a reason why it is commented out ;)

> When I do have them and the --encrypt option for pand on the NAP
> 
> rd@silverboxy:~$ ps uaxwww|grep pand|grep -v grep
> root     15840  0.0  0.1  1548  536 ?        Ss   23:32   0:00 /usr/bin/pand 
> --encrypt --listen --persist --role NAP --pidfile /var/run/pand.pid
> rd@silverboxy:~$ 
> 
> I still get pinless authentification (or they somehow match, though I tried to 
> make them different in all files).

Check with "hcidump -X -V" is you are not already paired and both sides
only authenticate with a link key. You can also use "hcitool auth" do
trigger the authentication by hand.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-05-07 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-07 20:03 [Bluez-users] pand seem to ignore any pin configurations Rainer Dorsch
2005-05-07 20:35 ` Marcel Holtmann
2005-05-07 21:39   ` Rainer Dorsch
2005-05-07 22:02     ` Marcel Holtmann [this message]
2005-05-08 13:08       ` Rainer Dorsch
2005-05-08 13:36         ` Marcel Holtmann
2005-05-08 15:27           ` Rainer Dorsch
2005-05-08 15:46             ` Marcel Holtmann
2005-05-08 16:24               ` Rainer Dorsch
2005-05-08 16:31                 ` Marcel Holtmann

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=1115503367.9031.31.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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