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

[Marcel Holtmann <marcel@holtmann.org>]

Hi Waldemar,

> 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
> +

I do not like this since it is really legacy stuff and makes since
really complicated. And now we are making big efforts to support this
and that is bad. Since Simple Pairing solved this nicely for us.

However I need to talk with Johan about this and figure something out.

Regards

Marcel