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

"Not on the same physical medium" security requirement for Tang server and clients #101

Open
jamshid opened this issue Nov 8, 2022 · 1 comment

Comments

@jamshid
Copy link

jamshid commented Nov 8, 2022

The README says it's important the Tang keys are not on the same physical medium when using a container, but that's not really docker/container-specific right? If the Tang server and a client are running in virtual machines on the same host and the server is stolen, the data can be unencrypted.

Docker Container
Tang is also available as a Docker Container.
Care should be taken to ensure that, when deploying in a container cluster, that the Tang keys are not stored on the same physical medium that you wish to protect.

IMO it would be good to move the "Tang keys must not be stored on the same physical medium that you wish to protect" requirement to https://github.com/latchset/tang/#security-considerations.

@jamshid jamshid changed the title "Same physical media" "Not on the same physical medium" security requirement for Tang server and clients Nov 8, 2022
@sarroutbi
Copy link
Collaborator

sarroutbi commented Nov 10, 2022

IMHO, it is worth to remember in the README.md that tang and clevis client should be pinned to different hosts for security issues. I agree it is not Docker specific, but it applies to Docker, so, it is worth reminding it there.

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

No branches or pull requests

2 participants