Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PW_SID:555789] Optionally require security for notify/indicate #1017

Closed
wants to merge 2 commits into from

Commits on Sep 30, 2021

  1. gatt: Allow GATT server to dicate CCC permissions

    Allow a GATT server to impose permissions/restrictions on a CCC by
    setting additional `X-notify` and `X-indicate` permissions on its
    associated characteristic.
    
    This allows a developer to require encryption/authentication in order
    for a GATT client to subscribe to server-initiated updates.
    
    Test procedure:
    Attempt to read/write with a "low" security level on an unprotected CCC
    using gatttool, and succeed
    Attempt to READ with a "low" security level on an protected CCC
    using gatttool, and succeed
    Attempt to WRITE with a "low" security level on an protected CCC
    using gatttool, and fail
    Attempt to read/write while paired on a protected CCC using
    `bluetoothctl`, and succeed
    Property404 authored and BluezTestBot committed Sep 30, 2021
    Configuration menu
    Copy the full SHA
    0a87692 View commit details
    Browse the repository at this point in the history
  2. doc/gatt-api: Add 'X-notify/X-indicate`

    Update docs to reflect the addition of the `X-notify` and `X-indicate`
    permissions, which allow a GATT server to restrict CCC write permissions
    via permissions set on its associated characteristic.
    Property404 authored and BluezTestBot committed Sep 30, 2021
    Configuration menu
    Copy the full SHA
    77d3d4d View commit details
    Browse the repository at this point in the history