From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] OBEX Push without pairing
Date: Tue, 01 Mar 2005 10:01:27 +0100 [thread overview]
Message-ID: <1109667687.17256.140.camel@pegasus> (raw)
In-Reply-To: <42242BAB.7080406@futurlink.com>
Hi Pedro,
> I am writing an applications that, among other things, sends an OBEX
> Push to a device (e.g. a mobile phone). This is working fine, except for
> one thing: whenever I send something to the device, the first time it
> always asks for the PIN. I have seen that, for example, kbluetooth (the
> KDE Bluetooth framework) and Impronto can send a file without pairing
> first. How can I do that?
>
> I am sure that I am missing something, but still have not found what. In
> my application, I call to socket(), bind() to a local address
> (BDADDR_ANY) and then connect(). It is at the connect stage that the
> pairing takes place. I have been following the code of kbluetooth and
> all I can see is that I am doing essentially the same.
it seems that your device is working in security mode 3 and then
actually every ACL connection requests the authentication. The simple
answer is to use security mode 1/2.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-01 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 8:45 [Bluez-users] OBEX Push without pairing Pedro Monjo Florit
2005-03-01 9:01 ` Marcel Holtmann [this message]
2005-03-01 10:14 ` Pedro Monjo Florit
2005-03-01 10:47 ` Marcel Holtmann
2005-03-01 10:50 ` Fred Schaettgen
2005-03-01 11:04 ` Pedro Monjo Florit
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=1109667687.17256.140.camel@pegasus \
--to=marcel@holtmann.org \
--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.