Skip to content

DOCS Question: How to add other ssh public keys to to authorized_keys #35

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

Open
brenzi opened this issue May 1, 2020 · 6 comments
Open
Labels
enhancement New feature or request

Comments

@brenzi
Copy link

brenzi commented May 1, 2020

No description provided.

@morelazers
Copy link
Contributor

There's currently no way to do this other than manually logging into the boxes and adding those keys.

In a future update we can modify the config to accept an array of other public keys that you would like to add.

@morelazers morelazers assigned morelazers and unassigned morelazers May 2, 2020
@rozifus
Copy link
Contributor

rozifus commented May 4, 2020

Added a ticket for docs with user information on adding ssh keys

Added a ticket for multiple ssh key support at instance creation time
*This may be a bit tricky as support will vary by provider but I think it would definitely be useful where we can support it

@rozifus
Copy link
Contributor

rozifus commented May 4, 2020

Actually on more thought we can probably add the key as part of the system provisioning after the instance is created, which should be identical across all providers

@brenzi
Copy link
Author

brenzi commented May 4, 2020

I think all providers offer to supply a bunch of pubkeys for their accounts. Maybe you could just keep these as they should be provisioned with any new droplet/vps/vm?

@morelazers
Copy link
Contributor

Yep @rozifus we can just take an array of keys in the config and push them into the sshUser/.ssh/authorized_keys file after provisioning.

@rozifus
Copy link
Contributor

rozifus commented May 6, 2020

@brenzi, While it would be good to get the ssh keys into the nodes as early as possible I think it will be much easier to implement as a single post-provisioning step that is provider agnostic. This would also mean if we add a provider in the future that only allows for a single ssh key on creation we won't run into any issues

@DrTexx DrTexx added the enhancement New feature or request label May 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants