Re: [PATCH 1/2] Add RequestSecurePinCode to agent API

["Gustavo F. Padovan" <padovan@profusion.mobi>]

* Waldemar Rymarkiewicz <waldemar.rymarkiewicz@tieto.com> [2011-06-08 16:05:19 +0200]:

> The method is called if min. 16 bytes pincode is mendatory
> to authenticate connection.
> 
> In practice this will be called only with mgmtops switched on. Hciops
> don't support secure pin code so far.
> ---
>  doc/agent-api.txt |   11 +++++++++++
>  1 files changed, 11 insertions(+), 0 deletions(-)
> 
> diff --git a/doc/agent-api.txt b/doc/agent-api.txt
> index 9ab2063..b1cb354 100644
> --- a/doc/agent-api.txt
> +++ b/doc/agent-api.txt
> @@ -31,6 +31,17 @@ Methods		void Release()
>  			Possible errors: org.bluez.Error.Rejected
>  			                 org.bluez.Error.Canceled
>  
> +		string RequestSecurePinCode(object device)
> +
> +			This method gets called when the service daemon
> +			needs to get the secure passkey for an authentication.
> +
> +			The return value should be a string of 16 characters
> +			length. The string can be alphanumeric.
> +
> +			Possible errors: org.bluez.Error.Rejected
> +			                 org.bluez.Error.Canceled
> +

Why RequestPinCode() isn't enough? It can accept up to 16 characters.
Alternatively we can add a Property to tell when to use pin code or not.

For BlueZ 5.0 we can break this and add a length param to RequestPinCode().

	Gustavo