Skip to content
This repository has been archived by the owner on Jun 2, 2021. It is now read-only.

Secure/audit key changes #128

Open
tttp opened this issue May 6, 2021 · 0 comments
Open

Secure/audit key changes #128

tttp opened this issue May 6, 2021 · 0 comments
Assignees

Comments

@tttp
Copy link
Member

tttp commented May 6, 2021

Setting up the encryption key is a very sensitive operation. I should be made much more visible:

  • send an email to all the org users:
    "IMPORTANT: proca encryption key changed"
    {username} has changed the encryption key (public key {}.
    As of now, all new data from your supporters are encrypted with that key and only {username}, or someone that has the matching private key, can decrypt the signatures. Please be sure it's properly and safely stored, without that private key, you will not be able to access your supporters data. We do not have a copy of it."

It's good to keep a log of the key changes, either as an audit log, or at least add a "owner" to the encryption key (key to the user), so we know who changed it

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

No branches or pull requests

2 participants