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

Encryption requires access to private key #3

Open
Enzime opened this issue Dec 12, 2024 · 4 comments
Open

Encryption requires access to private key #3

Enzime opened this issue Dec 12, 2024 · 4 comments

Comments

@Enzime
Copy link

Enzime commented Dec 12, 2024

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 as age keys

That would allow encryption to be done without requiring the private key or even 1Password at all

@bromanko
Copy link
Owner

bromanko commented Dec 14, 2024

I'm curious what you are trying to accomplish with this change. Why is it useful to encrypt without 1Password?

@Enzime
Copy link
Author

Enzime commented Dec 14, 2024

So that other people are able to send encrypted files to me with just my recipient and age-plugin-op installed or also it would allow me to create new files without unlocking my 1Password

I believe this is the case with other plugins like age-plugin-tpm and age-plugin-se

@bromanko
Copy link
Owner

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.

@Enzime
Copy link
Author

Enzime commented Dec 27, 2024

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 age-plugin-tpm as it uses the new experimental age plugin framework, feel free to check it out here:

https://github.com/Enzime/age-plugin-1p

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