From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 67058b: client/mgmt: Add options to ltks command for loadi...
Date: Wed, 03 Jun 2026 12:41:57 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1105509/000000-14aeb5@github.com> (raw)
Branch: refs/heads/1105509
Home: https://github.com/bluez/bluez
Commit: 67058b3f707cbd1acc867b598f471c744bd95f85
https://github.com/bluez/bluez/commit/67058b3f707cbd1acc867b598f471c744bd95f85
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-06-03 (Wed, 03 Jun 2026)
Changed paths:
M client/mgmt.c
Log Message:
-----------
client/mgmt: Add options to ltks command for loading entries
Add support for optionally specifying a single LTK entry when using
the ltks command. When called without arguments it clears all LTKs
(existing behavior). When called with an address and key parameters
it loads exactly one LTK entry, useful for testing.
Options:
-a addr_type Address type (1=LE Public, 2=LE Random)
-t key_type Key type (0=Unauthenticated, 1=Authenticated)
-c central Central flag (0 or 1)
-e enc_size Encryption key size (7-16)
-d ediv Encrypted Diversifier
-r rand Random number (64-bit)
-k key 128-bit key as 32 hex characters
Commit: 14aeb5480c3b59ad83320d712a0290949d524baa
https://github.com/bluez/bluez/commit/14aeb5480c3b59ad83320d712a0290949d524baa
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-06-03 (Wed, 03 Jun 2026)
Changed paths:
M doc/bluetoothctl-mgmt.rst
Log Message:
-----------
doc/bluetoothctl-mgmt: Update ltks command documentation
Document the new options for the ltks command including address type,
key type, central flag, encryption size, EDIV, random number and key
value parameters.
Compare: https://github.com/bluez/bluez/compare/67058b3f707c%5E...14aeb5480c3b
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-06-03 19:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1105509/000000-14aeb5@github.com \
--to=noreply@github.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