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

[Feature Request] Support for non-credential fields #212

Open
skewballfox opened this issue Jan 29, 2022 · 1 comment
Open

[Feature Request] Support for non-credential fields #212

skewballfox opened this issue Jan 29, 2022 · 1 comment

Comments

@skewballfox
Copy link

by non-credential fields I mean credit card info, addresses, and other sensitive fields saved by the browser if enabled. I'm thinking this should be something that can be handled without changes to gopass(though with more logic bridgeside) by treating fields as credentials.

The use case is this: all sensitive information would be encrypted at rest, and this drastically reduces risk in the event of compromised system: if they are using gopass, then all passwords are inaccessible, all information which could lead to identity theft or fraud could be inaccessible, all secrets and API keys could be inaccessible. The only point(s) of failure would be clipboard monitoring, compromising gopass, compromising the encryption backend(gpg or age), or compromising gopassbridge itself. plus it would be easy to use sensitive information across devices.

@martinhoefling
Copy link
Collaborator

If it can be realized without too much complexity in gopassbbridge we can think about it. I'm happy to assign the issue to someone who wants to build a PoC as a first step.

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

No branches or pull requests

2 participants