Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] pand seem to ignore any pin configurations
Date: Sun, 08 May 2005 18:31:29 +0200	[thread overview]
Message-ID: <1115569889.9031.133.camel@pegasus> (raw)
In-Reply-To: <200505081824.08678.rdorsch@web.de>

Hi Rainer,

> > > Not asking for a PIN each time is actually fine (persisten pairing is a
> > > nice invention;-). I just want to check that the system really wants to
> > > see a PIN when a new device comes in.
> > >
> > > Are you saying when I delete
> > >
> > > 	/etc/bluetooth/link_key
> > >
> > > on both NAP and PANU I should be askef for a password?
> >
> > Yes. And with bluez-utils-2.16 the link key storage has been changed.
> 
> Worked excellent, thanks. Are the link keys valid forever or do they have an 
> expiration date? I.e. if is do "security user" may it happen that bluez 
> simply stops working (because e.g. bluez is started before X and I won't 
> notice why until I figured out that the link key expired)

the link key don't expires. However using --secure with a recent kernel
you can force a change of the link key every time the connection was
successful.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-05-08 16:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-07 20:03 [Bluez-users] pand seem to ignore any pin configurations Rainer Dorsch
2005-05-07 20:35 ` Marcel Holtmann
2005-05-07 21:39   ` Rainer Dorsch
2005-05-07 22:02     ` Marcel Holtmann
2005-05-08 13:08       ` Rainer Dorsch
2005-05-08 13:36         ` Marcel Holtmann
2005-05-08 15:27           ` Rainer Dorsch
2005-05-08 15:46             ` Marcel Holtmann
2005-05-08 16:24               ` Rainer Dorsch
2005-05-08 16:31                 ` Marcel Holtmann [this message]

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