All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Use of /etc/bluetooth/link-key Bug or Feature ??
Date: Fri, 11 Mar 2005 00:10:14 +0100	[thread overview]
Message-ID: <1110496215.8511.0.camel@pegasus> (raw)
In-Reply-To: <200503090001.00828.jschindele@arcor.de>

Hi Juergen,

> by an error i misconfigured a link with autentification.
> so a entry in the file /etc/bluetooth/link-key was created.
> Then M. Holtmann helped me out and told me how to configure it right. 
> But From there on when a connection was demanded a link key request 
> was always sent even it AUTH was switched off.

if the other sides requests it, then this is correct.

> Is this a bug or a feature ??
>  If this is a feature how can i delete a unique entry for one device
> and not delete the whole file content because the content is not ascii ?

An ASCII based link key file is on the todo list.

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

  reply	other threads:[~2005-03-10 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-08 18:44 [Bluez-users] how to offer mysql service over bluetooth? S. M. Toufiqul Islam
2005-03-08  5:28 ` Brad Midgley
2005-03-08 23:01 ` [Bluez-users] Use of /etc/bluetooth/link-key Bug or Feature ?? Jürgen Schindele
2005-03-10 23:10   ` Marcel Holtmann [this message]
2005-03-11  1:07   ` Fred Schaettgen

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=1110496215.8511.0.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.