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

Encrypted messages #17

Open
kpcyrd opened this issue Jan 20, 2018 · 0 comments
Open

Encrypted messages #17

kpcyrd opened this issue Jan 20, 2018 · 0 comments

Comments

@kpcyrd
Copy link
Owner

kpcyrd commented Jan 20, 2018

Encryption is currently out of scope and needs to be done in a different layer if needed by encrypting the data before passing it to tr1pctl write. Since the blocks need to be decryptable in the future we can't apply forward secrecy, but having regular public key encryption built in might be useful and possibly a common usecase. The following scenario seems likely:

A sensor should be able to write an encrypted log which itself can verify, but can't actually read. To read the log, it needs to be transfered to a different, trusted system that has the private key that is needed to read the messages contained inside the blocks.

This would require a change to the file format, but I'm not yet sure how this would look like in detail. There could be a field in the block that identifies which publickey has been used so the trusted system can select the right private keys if it has multiple private keys. I'm not sure if encrypting to multiple public keys should be implemented.

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

1 participant