From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] auto pairing between client & server
Date: Wed, 27 Apr 2005 10:44:41 +0200 [thread overview]
Message-ID: <426F50F9.8090208@gmx.ch> (raw)
In-Reply-To: <1114542256.10706.329.camel@pegasus>
I'm not sure if we talk about the same thing.
On outgoing connections, when encryption is demanded, the pin_helper,
specified in hcid.conf is called and the output has to be like "PIN:1234".
If I wan't to use /etc/bluetooth/pin as this pin, I've to write a little
pin_helper that outputs this pin.
My question now is: is it with the bluez packages >= 2.16 possible to avoid
writing an own pin_helper? is hcid.conf configurable so that
/etc/bluetooth/pin is automatically used for outgoing connections?
regards
Marco
Marcel Holtmann wrote:
> Hi Marco,
>
>
>> > the PIN helper is a program with specific parameters and it must return
>> > on standard output "PIN:1234" for example or "ERR".
>>
>>Yes, I know. But you wrote in that email that prior to 2.16 this was
>>needed. That let's me assume that now it's possible to use the pin file for
>>outgoing connections too.
>
>
> this is correct. With 2.16 you can create a pincodes file.
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-04-27 8:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 20:06 [Bluez-users] auto pairing between client & server N. I.
2005-04-22 21:38 ` Marcel Holtmann
2005-04-24 16:17 ` Fredy P
2005-04-25 14:26 ` N. I.
2005-04-26 10:07 ` N. I.
2005-04-26 11:28 ` Marcel Holtmann
2005-04-23 21:31 ` Marco Trudel
2005-04-25 14:29 ` N. I.
2005-04-25 14:38 ` Marco Trudel
2005-04-26 10:02 ` N. I.
2005-04-26 10:44 ` Marco Trudel
2005-04-26 13:39 ` Marcel Holtmann
2005-04-26 11:31 ` Marcel Holtmann
2005-04-26 17:37 ` Marco Trudel
2005-04-26 17:46 ` Marcel Holtmann
2005-04-26 18:36 ` Marco Trudel
2005-04-26 19:04 ` Marcel Holtmann
2005-04-26 22:31 ` N. I.
2005-04-27 8:44 ` Marco Trudel [this message]
2005-04-27 8:50 ` Marcel Holtmann
2005-04-27 8:54 ` Marco Trudel
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=426F50F9.8090208@gmx.ch \
--to=mtrudel@gmx.ch \
--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