Repository navigation
onlykey-agent 1.1.16: composite PQC GPG keys, derived-v2 identities - #19
Merged
Merged
Conversation
onlykey
force-pushed
the
release-onlykey-agent-1.1.16
branch
from
September 28, 2026 17:30
9cd4416 to
d1318f8
Compare
onlykey
force-pushed
the
release-onlykey-agent-1.1.16
branch
3 times, most recently
from
October 12, 2026 21:00
ca32153 to
8d30637
Compare
onlykey
force-pushed
the
release-onlykey-agent-1.1.16
branch
2 times, most recently
from
October 23, 2026 16:24
e70f7ee to
6816745
Compare
For OnlyKey firmware v3.0.5 and python-onlykey 1.3.0. - Composite post-quantum GPG keys (libagent/device/onlykey_pqc.py): ML-KEM-768 + X25519 decryption and ML-DSA-65 + Ed25519 signing with keys in the PQC1-PQC4 slots, following draft-ietf-openpgp-pqc-10. - Derived identities v2: --skey/--dkey derived-v2 (or ECC32v2) selects the HKDF-based derivation (firmware v3.0.5+). The default is unchanged, so existing SSH and GPG keys stay the same. - The OnlyKey device module opens the HID handle once and always closes it on failure, and uses python-onlykey's shared challenge-code rule and response classifier (onlykey.protocol). - Packaging: onlykey-agent requires onlykey>=1.3.0 and lib-agent>=1.0.8, and Python 3.10+; PyPI project description added.
onlykey
force-pushed
the
release-onlykey-agent-1.1.16
branch
from
October 23, 2026 19:46
6816745 to
4793784
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One commit, for OnlyKey firmware v3.1.0 and python-onlykey 1.3.0 (trustcrypto/python-onlykey).
New
libagent/device/onlykey_pqc.py): ML-KEM-768 + X25519 decryption and ML-DSA-65 + Ed25519 signing, using keys in the PQC1–PQC4 slots. Follows draft-ietf-openpgp-pqc-10.--skey derived-v2/--dkey derived-v2(orECC32v2) selects the HKDF-based derivation, which needs firmware v3.1.0. The default is unchanged, so existing SSH and GPG keys stay the same.Packaging: onlykey-agent 1.1.16 requires
onlykey>=1.3.0(it importsonlykey.protocol),lib-agent>=1.0.8and Python 3.10+. It also gains a PyPI project description. The lib-agent version stays at 1.0.8, which is not on PyPI yet (PyPI has 1.0.6).Tests:
pytest libagentgives 80 passed and 1 failed. The failure istest_get_agent_sock_path, because there is nogpgconfon the test machine. On the firmware emulator, the onlykey-agent SSH tests, theonlykey-gpg inittests and the derived-v2 tests all pass (v1 default, v2 keys, ECDH, GPG init).Publish order: python-onlykey 1.3.0 first, then lib-agent 1.0.8, then onlykey-agent 1.1.16.
Related open PRs that overlap: #14 (X-Wing age), #13 and #16 (upstream sync).