From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] PIN Authentication Problems on MDV 2007
Date: Sun, 15 Oct 2006 15:11:00 +0200 [thread overview]
Message-ID: <1160917860.23675.7.camel@localhost> (raw)
In-Reply-To: <4531BD65.1020107@gmail.com>
Hi Manuel,
> I have updated to Mandriva 2007, and I can't figure why, I can't make
> things get back working, when I used mdv 2006 all bluez went on OK.
>
> Here is my hcid.conf:
> #
> # HCI daemon configuration file.
> #
>
> # HCId options
> options {
> # Automatically initialize new devices
> autoinit yes;
>
> # Security Manager mode
> # none - Security manager disabled
> # auto - Use local PIN for incoming connections
> # user - Always ask user for a PIN
> #
> security user;
>
> # Pairing mode
> # none - Pairing disabled
> # multi - Allow pairing with already paired devices
> # once - Pair once and deny successive attempts
> pairing multi;
>
> # Default PIN code for incoming connections
> passkey "1234";
>
> pin_helper /bin/bluepin;
>
> #dbus_pin_helper;
> }
>
> # Default settings for HCI devices
> device {
> # Local device name
> # %d - device id
> # %h - host name
> name "BlueZ (%d)";
>
> # Local device class
> class 0x3e0100;
>
> # Default packet type
> #pkt_type DH1,DM1,HV1;
>
> # Inquiry and Page scan
> iscan enable; pscan enable;
>
> # Default link mode
> # none - no specific policy
> # accept - always accept incoming connections
> # master - become master on incoming connections,
> # deny role switch on outgoing connections
> lm accept;
>
> # Default link policy
> # none - no specific policy
> # rswitch - allow role switch
> # hold - allow hold mode
> # sniff - allow sniff mode
> # park - allow park mode
> lp rswitch,hold,sniff,park;
> }
> ---
>
> /bin/bluepin is no more than a link to kbluetooth pin.
>
> The thing is that, when ever I try to establish a connection, it seems
> that BlueZ (or something else) is missing the PIN code.
>
> I'm doing:
> hcitool cc 00:50:C2:58:50:00 //To get the connection on
> hcitool key 00:50:C2:58:50:00 //To Exchange Link Kety,
>
> I have even tried with hcitool auth 00:50:C2:58:50:00, every time the
> result is the same.
>
> hcidump -X -V shows this:
> > HCI Event: PIN Code Request (0x16) plen 6
> bdaddr 00:50:C2:58:50:00
> < HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6
> bdaddr 00:50:C2:58:50:00
> > HCI Event: Command Complete (0x0e) plen 10
> PIN Code Request Negative Reply (0x01|0x000e) ncmd 1
> status 0x00 bdaddr 00:50:C2:58:50:00
> > HCI Event: Auth Complete (0x06) plen 3
> status 0x06 handle 1
> Error: PIN or Key Missing
>
> And I never get a Pin Request from the BlueZ side.
starting with bluez-utils-3.x the PIN helper concept has been replaced
with a passkey agent interface. You need to run a passkey agent to get
you PIN request dialog. One example would be bt-applet from the
bluez-gnome package.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-10-15 13:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 4:47 [Bluez-users] PIN Authentication Problems on MDV 2007 Manuel Naranjo
2006-10-15 13:11 ` Marcel Holtmann [this message]
2006-10-15 13:13 ` Manuel Naranjo
2006-10-16 1:08 ` Manuel Naranjo
2006-10-16 7:35 ` Marcel Holtmann
2006-10-17 16:21 ` Dietmar Segbert
2006-10-18 15:39 ` Stefan Seyfried
2008-06-02 17:51 ` Mats Karlsson
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=1160917860.23675.7.camel@localhost \
--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 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.