All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] auto pairing between client & server
Date: Tue, 26 Apr 2005 20:36:15 +0200	[thread overview]
Message-ID: <426E8A1F.7070707@gmx.ch> (raw)
In-Reply-To: <1114537612.10706.325.camel@pegasus>

 > 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.
Or how did you mean that?


regards
Marco


Marcel Holtmann wrote:
> Hi Marco,
> 
> 
>>>If you wanna do that with the bluez-utils prior 2.16 you need to write
>>>your own PIN helper program. With 2.16 you can use a pincodes file for
>>>these task.
>>
>>If I understand you right, it's possible to replace the pinhelper so that 
>>etc/bluetooth/pin is read for outgoing connections?
>>what's the configuration parameter?
>>pin_helper auto/file; ?
> 
> 
> the PIN helper is a program with specific parameters and it must return
> on standard output "PIN:1234" for example or "ERR".
> 
> 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

  reply	other threads:[~2005-04-26 18:36 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 [this message]
2005-04-26 19:04                 ` Marcel Holtmann
2005-04-26 22:31                   ` N. I.
2005-04-27  8:44                   ` Marco Trudel
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=426E8A1F.7070707@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 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.