public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SDP queries when authentication/encryption are turned on
Date: Mon, 28 Feb 2005 09:28:15 +0100	[thread overview]
Message-ID: <1109579295.17256.24.camel@pegasus> (raw)
In-Reply-To: <200502241322.06715.bluez-devel@schaettgen.de>

Hi Fred,

> > > > if you set your device into security mode 3, then this is what you get.
> > > > As I have often said, do this only when you know what you are doing and
> > > > what does this imply.
> > >
> > > Marcel, why don't you simply put this often repeated sentence into a
> > > comment in default hcid.conf right above auth/encrypt? If people are not
> > > familiar with bluetooth, then it's reasonable to assume that you have to
> > > enable this if you want any security at all. You don't expect everbody to
> > > know what security mode 3 means and what the alternatives are, do you?
> >
> > there is a comment that this is security mode 3, but actually this does
> > not prevents for its misuse and the later complaints. Problem is that
> > Bluetooth is still a complex technology and if you change defaults you
> > should understand what you are doing. However I always accept patches
> > that extends the manual pages with more details about it.
> 
> "should understand what you are doing"? Well, obviously this is wishful 
> thinking. You should really comment these settings right in the hcid.conf or 
> at least referr to the manpage. Then it's nearly impossible to change these 
> settings without reading the warnings about it. Not everyone will look into a 
> manpage, you should be more pragmatic here. It's your time that is wasted 
> with these questions after all ;)

even if I put a big explanation into the config file, people still will
do it wrong. Actually I think of removing some commands from the example
config file and only mentions their existens in the manual page or in
the source code.

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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-02-28  8:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23  2:08 [Bluez-devel] SDP queries when authentication/encryption are turned on Shawn Rutledge
2005-02-23  4:28 ` Marcel Holtmann
2005-02-23  9:44   ` Fred Schaettgen
2005-02-24 10:43     ` Marcel Holtmann
2005-02-24 12:22       ` Fred Schaettgen
2005-02-28  8:28         ` 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=1109579295.17256.24.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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