-
Notifications
You must be signed in to change notification settings - Fork 315
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
SSH should prompt to change ~/.ssh/config #355
Comments
Weird...I have the opposite problem. This is the error I see appearing in the logs
@pascalbreuninger Any idea? |
What system are you on @codeagencybe? The proposed solution would also solve your problem as we shouldn't run into permission issues inside of the |
It would be also better to only touch |
@levsha @codeagencybe you can run |
Hi, I stumbled across this behavior as well and find it very unfortunate that DevPod modifies my SSH config without my knowledge. This behavior does not seem to be mentioned in the docs. Furthermore, DevPod seems to modify the SSH config on every startup, regardless of whether the config already exists, and append it to the end. This actually breaks the SSH config for DevPod, if you use a glob host block before the DevPod config. For example:
The config after the glob block is unreachable because |
This worked for me
|
With v0.5.5 we prepend entries to the ssh config to avoid other configurations messing with the automated ones. Additionally you can alway set the context option to use a different config file: |
devpod cli v0.1.7
I was surprised to find my ~/.ssh/config file was modified without my permission. I understand the need, but that action should ask for confirmation before modifying.
It might be better to store config entries in their own file so ~/.ssh is not touched at all. Use the
-F
flag like sossh -F ~/.config/devpod/ssh.config SOME_NAME
The text was updated successfully, but these errors were encountered: