Hi Luiz,
> On Wed, Apr 22, 2015 at 12:14 AM, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>
>
> This add encryption flag which can be used when registering a service to
> require encryption when accessing a characteristic.
> ---
> doc/gatt-api.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/doc/gatt-api.txt b/doc/gatt-api.txt
> index 088d285..92118fd 100644
> --- a/doc/gatt-api.txt
> +++ b/doc/gatt-api.txt
> @@ -148,6 +148,7 @@ Properties string UUID [read-only]
> "authenticated-signed-writes"
> "reliable-write"
> "writable-auxiliaries"
> + "encryption"
>
> array{object} Descriptors [read-only]
>
> --
> 2.1.0
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I've actually been planning to send a patch to add a "Permissions"
property to GattCharacteristic1 and GattDescriptor1, which would be
more in line with GATT attribute permissions. What I had in mind was a
"Permissions" property, which would have array{string} as the type.
And potential values would be "read-encrypted", "read-authenticated",
etc. What do you think?
Thanks,
Arman
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
