-
Notifications
You must be signed in to change notification settings - Fork 3
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
Encryption requires access to private key #3
Comments
I'm curious what you are trying to accomplish with this change. Why is it useful to encrypt without 1Password? |
So that other people are able to send encrypted files to me with just my recipient and I believe this is the case with other plugins like age-plugin-tpm and age-plugin-se |
I see. That's a use case I haven't had. Seems handy. If you want to add it I'll give it a review/merge. |
I originally tried to make the changes to the plugin, but it ended up changing so much that I decided to rewrite it based off a newer version of |
I think that the identity struct should also contain the public key corresponding to the SSH key stored in 1Password
The relevant code in
agessh
is https://github.com/FiloSottile/age/blob/main/agessh/agessh.go#L144-L166, we could use this package and call some of the relevant functions to help with using SSH keys asage
keysThat would allow encryption to be done without requiring the private key or even 1Password at all
The text was updated successfully, but these errors were encountered: