Skip to content

Expose secret in a virtual filesystem #931

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

Closed
mcanevet opened this issue Sep 16, 2018 · 3 comments
Closed

Expose secret in a virtual filesystem #931

mcanevet opened this issue Sep 16, 2018 · 3 comments
Labels
feature Enhancements and new features help-wanted
Milestone

Comments

@mcanevet
Copy link

It would be nice to have some kind of virtual filesystem to transparently expose secrets as files (maybe using Fuse).
A lot of applications can take their passphrase to unlock internal secret manager from a file. It would be nice to keep it stored in a gopass store and not have to unseal it in a file on the real filesystem.

@dominikschulz dominikschulz added feature Enhancements and new features help-wanted labels Sep 16, 2018
@dominikschulz dominikschulz added this to the 1.x.x milestone Sep 16, 2018
@dominikschulz
Copy link
Member

How do you want to protect this virtual filesystem against unauthorised access?
I think having "random" passphrase prompts pop up when an application in the background accesses your FUSE store might be prone to abuse.

@martinhoefling
Copy link
Contributor

One solution to your problem if injecting environment variables containing secrets are an option is summon. See https://www.schwabenlan.de/en/post/2018/01/combining-gopass-and-summon/ and https://github.com/gopasspw/gopass/blob/master/docs/summon-provider.md

@mcanevet
Copy link
Author

@martinhoefling great solution, I didn't know summon. This looks nice. I'll have a look at it. Thanks a lot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Enhancements and new features help-wanted
Projects
None yet
Development

No branches or pull requests

3 participants