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

Investigations into a Random Read and Random Write State Substrate for Keynodes #2

Closed
CMCDragonkai opened this issue Jul 3, 2018 · 4 comments
Assignees
Labels
research Requires research

Comments

@CMCDragonkai
Copy link
Member

CMCDragonkai commented Jul 3, 2018

Ideally we would want to be able to change secrets (that is write more secrets to a secret repo, remove secrets from a secret repo, or even change the size of a secret file) randomly without doing linear operations like re-encryption and re-serialisation of archive formats. This may even help secret sharing to be more efficient in the future.

@CMCDragonkai
Copy link
Member Author

Consider existing secret database tech like sqlite.

@CMCDragonkai
Copy link
Member Author

@CMCDragonkai
Copy link
Member Author

CMCDragonkai commented Sep 27, 2018

These 2 projects use FUSE to mediate between a filesystem in userspace and encrypted backend on disk somewhere. FUSE is interesting because we can offer a standard FS interface to consumers of Polykey secrets. But to be really secure you would have to either use mount namespaces or file descriptors as capabilities to allow specific processes to access secrets.

FUSE is not portable to mobile devices.

@MeanMangosteen
Copy link
Contributor

#7 Merged into this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
research Requires research
Development

No branches or pull requests

2 participants