From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hcid.conf : security auto - pairing
Date: Wed, 21 Sep 2005 11:32:31 +0200 [thread overview]
Message-ID: <1127295151.495.22.camel@localhost.localdomain> (raw)
In-Reply-To: <432E89E8.3040809@ubuntu.com>
Hi Charles,
> Issint the "auto" option suppose to work for outgoing connections also?
>
> when I do ....
>
> bash$ rfcomm connect 0 xx:xx:xx:xx:xx:xx
>
> my cellphone askes for a pin, I type it in and then the cumputer it
> brings up bluepin asking for a pin. issint is suppose to the the default
> one in /etc/bluetooth/pin ?
the /etc/bluetooth/pin is only used for incoming connection. For
outgoing connections the /var/lib/bluetooth/<bdaddr>/pincodes can be
used. Look at the source code for details, because I never made this
feature public.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-09-21 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 9:50 [Bluez-devel] hcid.conf : security auto - pairing Charles Majola
2005-09-19 10:20 ` [Bluez-devel] pairing problem Charles Majola
2005-09-21 9:31 ` Marcel Holtmann
2005-09-30 8:11 ` Charles Majola
2005-09-30 8:16 ` Marcel Holtmann
2005-09-30 8:27 ` Charles Majola
2005-09-21 9:32 ` Marcel Holtmann [this message]
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=1127295151.495.22.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).