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] Re: RFCOMM service level security testing
Date: Mon, 15 Nov 2004 19:10:11 +0100	[thread overview]
Message-ID: <1100542211.7208.66.camel@pegasus> (raw)
In-Reply-To: <loom.20041115T183351-61@post.gmane.org>

Hi David,

> Please keep in mind that a device that has been authenticated and even 
> authorized does not necessarily mean it is trusted.  I believe that trusted 
> means that the user does not need to "ok" a secure connection using 
> Authorization for each time it connects.  Some services may wish to have a 
> device be authorized each time it connects to a particular service (profile), 
> even though the device has been previously paired.

this is correct, but this is another topic and for that we need a policy
manager that will take care of it.

> also, regarding enabling/disabling encrypted links...there are a few 
> controllers out there that REQUIRE encyption to be disabled before allowing a 
> Role Switch.  So being able to disable encrption and reenable it Must be an 
> option (without disconnecting RFCOMM and/or L2CAP channels).  There is 
> currently a Bluetooth design proposal to require the controllers to perform 
> this logic...but it is still at an early revision phase, and therefore won't 
> be a requirement for a long time.  This also shows that an application WILL 
> need to be able to talk directly to HCI when it has l2cap and/or rfcomm 
> channels that are active.  When apps start getting more sophisticated and need 
> to allow lots of profiles (Such as phones, PCs, and PDAs), they need to manage 
> the Controller for roles, power management, eSCO, etc.

In general there should be no need to switch the role more than once. I
only must make sure that the role switch is finished before we enable
the encryption.

According to the HCI I really like to avoid that any profile related
applications talk directly to it. This shouldn't be needed.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel/listinfo/bluez-devel

      reply	other threads:[~2004-11-15 18:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 15:55 [Bluez-devel] RFCOMM service level security testing Marcel Holtmann
2004-11-02 22:03 ` Marcel Holtmann
2004-11-03 15:28   ` Stephen Crane
2004-11-03 15:37     ` Marcel Holtmann
2004-11-03 15:56       ` Stephen Crane
2004-11-03 16:08         ` Marcel Holtmann
2004-11-03 16:38           ` Stephen Crane
2004-11-05 12:28             ` Marcel Holtmann
2004-11-03 16:49         ` Steven Singer
2004-11-03 17:52           ` Marcel Holtmann
2004-11-03 18:45             ` Steven Singer
2004-11-03 19:01               ` Marcel Holtmann
2004-11-15 17:58                 ` [Bluez-devel] " David Hughes
2004-11-15 18:10                   ` 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=1100542211.7208.66.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