From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Help with bluez pairing problem!!
Date: Mon, 18 Jul 2005 13:30:58 +0200 [thread overview]
Message-ID: <1121686258.22662.80.camel@pegasus> (raw)
In-Reply-To: <IJTM7X$1B27DB0B4797131F8B5DE564475869A0@libero.it>
Hi Andrea,
> i have a problem with pairing in a scenario where a pc tries to push (via obex) a file to a cell phone. I set up all my environment and all works fine, on my cell the PC PIN is requested and after i enter it the file is trasmitted and all goes fine. But i ve this kind of problem:
>
> After the first authentication i still need (for my project requirementes) that next pushes to the cell ask again for PIN. To do this i think i suppose i need to delete (on my cell phone side or on my pc side) the authentication info. I need to do it on my pc, but how can i programmatically delete a pairing entry from the link_key file ?
the newer bluez-utils version don't use /etc/bluetooth/link_key file
anymore. See my posting for details.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-07-18 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 11:21 [Bluez-devel] Help with bluez pairing problem!! andi.c
2005-07-18 11:30 ` Marcel Holtmann [this message]
2005-07-18 13:22 ` Frederic Danis
2005-07-18 15:16 ` Marcel Holtmann
2005-07-18 11:40 ` gao.yingbin
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=1121686258.22662.80.camel@pegasus \
--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