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

security: move away from SSH keys stored in cleartext #1603

Open
ltalirz opened this issue Jun 13, 2023 · 3 comments
Open

security: move away from SSH keys stored in cleartext #1603

ltalirz opened this issue Jun 13, 2023 · 3 comments
Labels
kind/feature New feature request

Comments

@ltalirz
Copy link
Contributor

ltalirz commented Jun 13, 2023

Currently, the terraform deployment step results in the hpcadmin SSH key being stored in cleartext in the volume of the deployer, which allows for lateral movement in the network.

It would be preferable to use a local key management solution, such as password-protected (encrypted) SSH keys with an SSH agent and a timeout for ssh-add (e.g. 24h).

@ltalirz ltalirz added the kind/bug Something isn't working label Jun 13, 2023
@ltalirz
Copy link
Contributor Author

ltalirz commented Jun 13, 2023

Edit: this should have been a feature request rather than a bug

@xpillons xpillons added kind/feature New feature request and removed kind/bug Something isn't working labels Jun 14, 2023
@xpillons
Copy link
Collaborator

can you please elaborate more on this ? moving to bicep would remove that I guess.

@ltalirz
Copy link
Contributor Author

ltalirz commented Jun 15, 2023

This was flagged by an automatic security scanner of a customer.

I think the basic premise is simply that storing SSH keys in cleartext (time-unlimited token) on a web server allows an attacker who gains access to the machine to move laterally through the network and should be avoided.

Thinking a bit more about this, I guess in the case of a compromise of the deployer VM, the main worry is actually the (permanent) system managed identity rather than the SSH key for the cluster.
Perhaps one could suggest users to shut down the deployer when it's not used to reduce the attack surface.

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

No branches or pull requests

2 participants