Support for p256tag and p256mlkem768tag recipients
Open
Nobody has claimed this yet.
keyservice/age
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Currently, when using an identity generated by age-plugin-tpm like age1tag1..., this is the output of sops encrypt:
Could not generate data key: [failed to encrypt new data key with master key "age1tag1...": failed to create writer for encrypting sops data key with age: failed to wrap key for recipient #0: tag plugin: couldn't start plugin: "tag" plugin not found: exec: "age-plugin-tag": executable file not found in $PATH]
Invoking age itself with the identity works fine. I think support for p256tag and p256mlkem768tag is generally missing. The old tpm tag works fine.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with sops encrypt and an age-plugin-tpm identity using the p256tag or p256mlkem768tag recipient forms. Trace the age recipient handling and compare it with the existing TPM tag support; done means these recipients encrypt successfully while the old TPM tag continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100