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

Support github id based public key encryption #1409

Open
ysmood opened this issue Jan 9, 2024 · 0 comments
Open

Support github id based public key encryption #1409

ysmood opened this issue Jan 9, 2024 · 0 comments

Comments

@ysmood
Copy link

ysmood commented Jan 9, 2024

I want to achieve something like this:

sops --encrypt --whisper @rsc conf.yaml

The line above will encrypt the conf.yaml for github users rsc, every user's public key is always public available on github, such as https://github.com/rsc.keys, just append the .keys to a user's profile page url.

With this style, we don't have ask the recipient to generate new keys and send it to the maintainer, as long as they can push the repo they can decrypt the sops file, able to push means already has a public key uploaded to github. Same works for other platforms like gitlab.

I made a Age like tool for it: whisper.

My question is it easy to add new encryption tool to sops, are there guidelines or convention I need to follow to make a PR? I have read the CONTRIBUTING.md.

I'm aware of that #1134 is a year old, also sops age does't support key passphrase yet.

FYI: The comparison between age and whisper.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant