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 11:47:56 +0100 [thread overview]
Message-ID: <1109674076.17256.143.camel@pegasus> (raw)
In-Reply-To: <42244089.7010906@futurlink.com>
Hi Pedro,
> > 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.
> >
> Thank you for your fast answer.
>
> I am not quite sure about the security mode the device is. How can I
> get it? In any case, I have executed (as root):
>
> $ hciconfig hci0 noencrypt
> $ hciconfig hci0 noauth
>
> but still no success. With the same computer and configuration and as
> a normal user, if I send a file from KDE using kbtobexclient, it works
> as expected (no PIN requested, just the confirmation for receiving the
> message), so I believe that there is some other things to do. I guess
> that it should be a library call or somthing similar. Any suggestions?
run "hcidump -X -V" as root at the same time and show us the result.
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 10:47 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
2005-03-01 10:14 ` Pedro Monjo Florit
2005-03-01 10:47 ` Marcel Holtmann [this message]
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=1109674076.17256.143.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.