From: "Fred Schättgen" <Sch@ttgen.net>
To: bluez-devel@lists.sourceforge.net
Cc: Marcel Holtmann <marcel@holtmann.org>,
Julien Campana <juliencampana@yahoo.fr>
Subject: Re: [Bluez-devel] Encryption, authentication with Bluez
Date: Wed, 5 May 2004 16:04:50 +0200 [thread overview]
Message-ID: <200405051604.51052.Sch@ttgen.net> (raw)
In-Reply-To: <1083761997.4420.4.camel@pegasus>
On Wednesday 05 May 2004 14:59, Marcel Holtmann wrote:
> Hi Julien,
>
> > With the hciconfig tool, authentication and encryption can be switch to
> > on/off.
> > But if I well understood, this affects the local device and therefore
> > every future connection.
>
> if you switch auth and encrypt on with hciconfig or in hcid.conf then
> you are in security mode 3.
>
> > Is there any way to have two connections, one using authentication and
> > not the other?
>
> This is security mode 2 (also called service level security) and of
> course this is possible. You can trigger auth or switch encryption with
> hcitool.
Marcel, some time ago you said you were planning to add an ioctl to let
regular users trigger an authentication request. Is this possible in the
meantime? Or are there any reasons why this isn't a good idea?
It would be very useful for our KDE stuff (obex push -> no authentication,
other services -> authentication required). Otherwise I'd have to work around
it with a small suid helper to ask for authentication, but I really want to
avoid a hack like that.
regards
Fred
--
Fred Schaettgen
Sch@ttgen.net
next prev parent reply other threads:[~2004-05-05 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 11:53 [Bluez-devel] Encryption, authentication with Bluez Julien Campana
2004-05-05 12:59 ` Marcel Holtmann
2004-05-05 14:04 ` Fred Schättgen [this message]
2004-05-05 14:25 ` Marcel Holtmann
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=200405051604.51052.Sch@ttgen.net \
--to=sch@ttgen.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=juliencampana@yahoo.fr \
--cc=marcel@holtmann.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