Investigate age plugin-opportunities · Issue #1 · stevelr/age-op · GitHub
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

Investigate age plugin-opportunities #1

Open
stevelr opened this issue May 30, 2023 · 1 comment
Open

Investigate age plugin-opportunities #1

stevelr opened this issue May 30, 2023 · 1 comment

Comments

@stevelr
Copy link
Owner

stevelr commented May 30, 2023

There are two potential age plugin opportunities:

  1. use an age plugin that retrieves secrets from environment variables (such a plugin does not exist yet, or at least isn't listed in the plugin index on awesome-age). This would allow us to eliminate the need to write the private key to disk. To minimize risk of exposure, the secret is written with a random file name, has read access limited to the current user (or root), and the file is immediately deleted after it's used. A plugin that lets age read the identity from an environment variable would mitigate that risk.

  2. Could a plugin perform the 1password integration? I haven't read the plugin api so I don't know yet if it's possible or if it's a good idea.

@stevelr stevelr changed the title Investigate plugin-opportunities Investigate age plugin-opportunities May 30, 2023
@bromanko
Copy link

I created age-plugin-op, an age plugin that sources SSH keys from 1Password using the op CLI. I couldn't use the age-op script because I was wanting to integrate with a tool (homeage) that integrated directly with age.

Would love any feedback or comments if you have a chance to take a look.

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

2 participants