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

feature request: reuse user ssh keys #647

Closed
m-ildefons opened this issue Apr 25, 2022 · 0 comments · Fixed by #651
Closed

feature request: reuse user ssh keys #647

m-ildefons opened this issue Apr 25, 2022 · 0 comments · Fixed by #651

Comments

@m-ildefons
Copy link
Contributor

It would be a neat quality of life improvement if sesdev could reuse the users ssh keys instead or in addition to its custom keys. Some possible use cases are:

  • running ansible from the developers workstation
  • the QA Maintenance cli tool, which needs ssh access to gather environmental information

An implementation should consider that some users use an ssh-agent and do not have keys in ~/.ssh. The public keys can be fetched with ssh-add -L in that case. If this feature requires config flags, it would be great to be able to persist them in ~/.sesdev/config.yaml.

m-ildefons added a commit to m-ildefons/sesdev that referenced this issue May 17, 2022
- Add feature to provision additional ssh public keys to the VM's
  `/root/.ssh/authorized_keys` file.

This feature allows a user to specify a list of key ids. The public keys
belonging to those ids will be fetched from the ssh agent and
provisioned to the VM's `/root/.ssh/authorized_keys` file. This allows
for better interaction with tools like `mtui`, which don't utilize
`sesdev` as ssh wrapper but still need ssh access to the VMs.

fixes: SUSE#647
Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
m-ildefons added a commit to m-ildefons/sesdev that referenced this issue May 24, 2022
- Add feature to provision additional ssh public keys to the VM's
  `/root/.ssh/authorized_keys` file.

This feature allows a user to specify a list of key ids. The public keys
belonging to those ids will be fetched from the ssh agent and
provisioned to the VM's `/root/.ssh/authorized_keys` file. This allows
for better interaction with tools like `mtui`, which don't utilize
`sesdev` as ssh wrapper but still need ssh access to the VMs.

fixes: SUSE#647
Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
m-ildefons added a commit to m-ildefons/sesdev that referenced this issue May 25, 2022
- Add feature to provision additional ssh public keys to the VM's
  `/root/.ssh/authorized_keys` file.

This feature allows a user to specify a list of key ids. The public keys
belonging to those ids will be fetched from the ssh agent and
provisioned to the VM's `/root/.ssh/authorized_keys` file. This allows
for better interaction with tools like `mtui`, which don't utilize
`sesdev` as ssh wrapper but still need ssh access to the VMs.

fixes: SUSE#647
Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant