Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] remove pairing with device?
Date: Wed, 08 Dec 2004 09:42:19 +0100	[thread overview]
Message-ID: <1102495339.9988.31.camel@pegasus> (raw)
In-Reply-To: <OF0770A93A.BF533453-ONC1256F64.002DB738-C1256F64.002F0A9E@isbac.com>

Hi Marius,

> I've gotten BlueZ and OpenObex to work, so I can send files from my phone 
> to my linux box. I read the pin from /etc/bluetooth/pin. 
> That works very well. But once the phone is paired with Bluez, I can 
> change the pin of BlueZ, but the phone stays paired and won't ever ask for 
> the new pin. When I delete the pairing on the phone, it will ask for the 
> new pin, I need to delete the pairing on the BlueZ side. Is that possible?

the link keys are stored in binary form in /etc/bluetooth/link_key. Look
at the mailing list archive for details about that. There has been a
thread lately.

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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-12-08  8:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08  8:33 [Bluez-users] remove pairing with device? Marius Schaefer/Camberg/ISBAC
2004-12-08  8:42 ` Marcel Holtmann [this message]
2004-12-08  8:50   ` Marius Schaefer/Camberg/ISBAC

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=1102495339.9988.31.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox