Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

security questions #21

Open
wgahnagl opened this issue Jul 30, 2019 · 1 comment
Open

security questions #21

wgahnagl opened this issue Jul 30, 2019 · 1 comment
Labels
question Further information is requested

Comments

@wgahnagl
Copy link
Collaborator

Right now, it's easy to see that even sensitive data is being stored in an insecure way though sqlite. We haven't really come to a conclusion on how we're going to fix something like that. It's more secure than typing your password into a shareable notebook, but it's just about as secure as saving your passwords in a file on your machine.

we were thinking of adding a -s flag when setting a parameter, and encrypting the db, but that would also make it difficult to share scenes.

We were thinking of encrypting with gpg, to allow people to share public keys and access encrypted sqlite dbs.

@wgahnagl wgahnagl added the question Further information is requested label Jul 30, 2019
@wgahnagl wgahnagl changed the title security security questions Jul 30, 2019
@abertsch72
Copy link
Collaborator

one possibility that could make scene sharing easier if we take the encryption route: we could add a "share scene" feature (or some equivalent that avoids "ss"), where a copy of the scene is decrypted except for secret-marked parameters, which are deleted ?

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

No branches or pull requests

2 participants