linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Szymon Janc <szymon.janc@gmail.com>
Subject: [RFC 2/2] doc: Add reauthentication support to Agent API
Date: Tue, 14 May 2013 23:23:15 +0200	[thread overview]
Message-ID: <1368566595-8836-3-git-send-email-szymon.janc@gmail.com> (raw)
In-Reply-To: <1368566595-8836-1-git-send-email-szymon.janc@gmail.com>

Add ReauthenticationPolicy property to AgentManager1 interface.
This will allow to change default reauthentication  policy.

Add RequestReauthentication method to Agent API. This method will
be used to request user consent for remote device reauthentication.
---
 doc/agent-api.txt |   43 ++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 42 insertions(+), 1 deletion(-)

diff --git a/doc/agent-api.txt b/doc/agent-api.txt
index 2e70931..0074259 100644
--- a/doc/agent-api.txt
+++ b/doc/agent-api.txt
@@ -9,7 +9,7 @@ Service		org.bluez
 Interface	org.bluez.AgentManager1
 Object path	/org/bluez
 
-		void RegisterAgent(object agent, string capability)
+Methods		void RegisterAgent(object agent, string capability)
 
 			This registers an agent handler.
 
@@ -61,6 +61,32 @@ Object path	/org/bluez
 
 			Possible errors: org.bluez.Error.DoesNotExist
 
+Properties	string ReauthenticationPolicy [readwrite]
+
+			Default policy for reauthentication of already paired
+			devices. UI entity should clearly inform user about
+			possible cause and possible security consideration of
+			reauthentication before changing value of this
+			property.
+
+			Following policies are possible:
+			  - disallow reauthentication
+			  - ask for user consent before reauthentication
+			    (see  RequestReauthentication from Agent API)
+			  - allow reauthentication without user consent
+
+			Some of possible causes of already paired remote device
+			missing linkkey:
+			  - unpair performed by user on remote device only
+			  - reset of a remote device e.g. due to user action or
+			    power source depletion
+			  - lost of linkkey on remote device due to pairing with
+			    secondary OS or other host
+			  - bogus device is imitating user's legitimate device
+			    (security issue if reauthentication occurs!)
+
+			Possible values: "ask", "allow" or "disallow"
+
 
 Agent hierarchy
 ===============
@@ -176,6 +202,21 @@ Methods		void Release()
 			Possible errors: org.bluez.Error.Rejected
 			                 org.bluez.Error.Canceled
 
+		void RequestReauthentication(object device)
+
+			This method gets called to request the user for consent
+			to perform reauthentication of already paired device.
+
+			Agent should inform user about possible cause and
+			security considerations related to this request. Please
+			see ReauthenticationPolicy property description in
+			Adapter API for details.
+
+			If this method is not implemented consent is rejected.
+
+			Possible errors: org.bluez.Error.Rejected
+			                 org.bluez.Error.Canceled
+
 		void Cancel()
 
 			This method gets called to indicate that the agent
-- 
1.7.10.4


      parent reply	other threads:[~2013-05-14 21:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 21:23 [RFC 0/2] Reauthentication support Szymon Janc
2013-05-14 21:23 ` [RFC 1/2] doc: Add reauthentication commands and event to Management API Szymon Janc
2013-05-14 23:15   ` Vinicius Costa Gomes
2013-05-27 18:50     ` Szymon Janc
2013-05-27 18:57       ` Marcel Holtmann
2013-05-30 22:10         ` Szymon Janc
2013-05-14 21:23 ` Szymon Janc [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=1368566595-8836-3-git-send-email-szymon.janc@gmail.com \
    --to=szymon.janc@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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).