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

[Security] A feature to encrypt sensitive parts of an existing message #263

Closed
jstanden opened this issue Jun 27, 2017 · 2 comments
Closed
Projects
Milestone

Comments

@jstanden
Copy link
Owner

Like Keybase, but for people who send logins and other sensitive information in plain email.

@jstanden
Copy link
Owner Author

jstanden commented Oct 6, 2017

This would be easier to do now with the GPG public keys.

@jstanden jstanden added this to To do in 9.6 via automation Apr 29, 2020
@jstanden jstanden added this to the 9.6 milestone Apr 29, 2020
@jstanden
Copy link
Owner Author

jstanden commented Jun 6, 2020

Implemented in 9.6

@jstanden jstanden closed this as completed Jun 6, 2020
9.6 automation moved this from To do to Done Jun 6, 2020
jstanden added a commit that referenced this issue Aug 8, 2020
…This targets one or more public keys by chooser and/or ID. An arbitrary message is encrypted and saved to a placeholder in PGP ASCII format. This makes it easy to implement an 'Encrypt' form interaction on public key records. It could also be used by customer-facing forms to encrypt form responses.

Fixes #263
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
9.6
  
Done
Development

No branches or pull requests

1 participant