Support encryption with x.509 cert in win certmgr
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
In an environment where no KMS is available, but a corporate PKI is in place, it would be very handy to encrypt data with a personal X.509 certificate.
To do so I propose to use the Protect-CmsMessage Cmdlet of PowerShell.
This could also be invoked via WSL on Windows by calling powershell.exe.
This Cmdlet also supports key selection, which could be similar to PGP.
I'm not sure about the contribution process. Should I come up with some demo code?
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
No source files or tests are identified in the issue. Start by reviewing how SOPS currently selects encryption backends, then investigate invoking PowerShell's Protect-CmsMessage directly or through powershell.exe from WSL. Done should include X.509 certificate selection and successful encryption in environments without a KMS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100