From: Miguel <mc354@tid.es>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] bluetooth mobile connection without pin request
Date: Mon, 14 Jan 2008 17:38:56 +0100 [thread overview]
Message-ID: <1200328736.6259.21.camel@McM> (raw)
Hello,
I ' m trying to connect my mobile phone with my laptop using the
following:
sudo rfcomm connect 0 00:17:E3:04:8E:89
in this way, I get a serial device attached to /dev/rfcomm0 after pin
exchanging between the mobile and the laptop.
is there any way no to request the pin when pairing the devices?
If I ' m not using gnome, how can manage the key exchange?
thank you in advance,
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2008-01-14 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 16:38 Miguel [this message]
2008-01-14 20:01 ` [Bluez-users] Problems pairing a Treo 650 Robert Moskowitz
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=1200328736.6259.21.camel@McM \
--to=mc354@tid.es \
--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.