Re: [Bluez-users] Pin Authentication

["Przemysław Jakubowski" <przemyslaw.jakubowski@javatech.com.pl>]

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

It's working, thank you very much.

Best Regards, Przemek

2007/8/29, Mats Erik Andersson <mats@blue2net.com>:
>
> ons 2007-08-29 klockan 11:52 +0200 skrev Przemysław Jakubowski:
> > I use BlueZ 2.25, and I have to use it.
> > Now I have set security auto, and pin_helper /usr/bin/bluepin where
> > bluepin is a file with 1234.
> > Is it correct configuration??
> >
> > Regards, Przemek
> >
> In system with bluez-utils 2.* any pin-code helper have
> to output a string "PIN:1234" in order to be accepted.
> Thus
>         #!/bin/sh
>         logger -t hicd.pin-helper "Disclosed my pin-code"
>         echo "PIN:1234"
>
> would be useful for a fixed authentification. But as stated
> by Marcel Holtmann, presentday bluez-utils 3.* are using
> clearly superior mechanisms, so think trough what systems
> you are using.
>
> Regards
>
> M E Andersson
>
>
>
> > 2007/8/29, Marcel Holtmann <marcel@holtmann.org>:
> >         Hi,
> >
> >         > I want to configure my computer, that accepts connection
> >         with some
> >         > defined default PIN.
> >         > How I should configure hcid.conf?
> >         > What I should insert in security , auto, none, or user.
> >         > Should I use passkey "1234" or maybe
> >         pin_helper /usr/bin/bluepin , and
> >         > bluepin is file with 1234.
> >         > Should I set maybe something else?
> >
> >         if you use a default PIN, then you also can use no PIN at all.
> >         Anyway
> >         starting with BlueZ 3.x you need a passkey agent.
> >
> >         Regards
> >
> >         Marcel
> >
> >
> >
> >
> -------------------------------------------------------------------------
> >         This SF.net email is sponsored by: Splunk Inc.
> >         Still grepping through log files to find problems?  Stop.
> >         Now Search log events and configuration files using AJAX and a
> >         browser.
> >         Download your FREE copy of Splunk now
> >         >>  http://get.splunk.com/
> >         _______________________________________________
> >         Bluez-users mailing list
> >         Bluez-users@lists.sourceforge.net
> >         https://lists.sourceforge.net/lists/listinfo/bluez-users
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________ Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

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

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

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

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

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