linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Alec <bluez@cormack.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Bluez NAP refuses connection if PANU clent has	deleted pairing.
Date: Tue, 20 Jun 2006 15:56:53 +0200	[thread overview]
Message-ID: <1150811813.18381.44.camel@localhost> (raw)
In-Reply-To: <4497E167.3020205@cormack.org>

Hi Alec,

> Thanks for the reply.  I will try to get a later version of bluez-utils 
> then update the mailing list with the outcome.

always reply to the mailing list. There is no point in moving this to a
private discussion.

> I just wanted to clarify one point first about not using auth and 
> encrypt (mode 3). 

If you set auth and encrypt in hcid.conf (which got removed in
bluez-utils-3.1 btw) then you are in security mode 3. You really don't
wanna do that and for the why you simply look at the mailing list
archive, because this has been discussed multiple times.

> Do you mean just that I shouldn't use them in hcid.conf and only use 
> them when I start the pand daemon?  Or is there some problem using both 
> options together?

The pand has the options -A (for auth) and -E (for encrypt) and this
gives you security mode 2 which is what you really want.

Regards

Marcel




_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2006-06-20 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 17:11 [Bluez-users] Bluez NAP refuses connection if PANU clent has deleted pairing Alec
2006-06-20  9:55 ` Marcel Holtmann
     [not found]   ` <4497E167.3020205@cormack.org>
2006-06-20 13:56     ` Marcel Holtmann [this message]
2006-06-20 15:02       ` Alec

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=1150811813.18381.44.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=bluez@cormack.org \
    /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;
as well as URLs for NNTP newsgroup(s).