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

error during SSH connection #171

Closed
yakhatape opened this issue Jan 17, 2024 · 2 comments
Closed

error during SSH connection #171

yakhatape opened this issue Jan 17, 2024 · 2 comments

Comments

@yakhatape
Copy link

I got the following error :

Shell opener command was unsuccessful:
command-line line 0: unsupported option "accept-new".

image

Due to the option of the command formated by XPIPE :
ssh XXXX -oStrictHostKeyChecking=accept-new -oConnectTimeout=5 -t

This parameter should be an option in the hand of enduser

@crschnick
Copy link
Contributor

So first of all, I think that this option is not supported in very old SSH client versions, you can check which version you are running with ssh -V and upgrade to a newer version if possible, also for all the security fixes included in newer versions.

About whether the option should be set by default, I just enabled it by default as I have never encountered someone who checked the host key for a hostname if there was no conflict before. If the known host key changes, you will still get the warning pop up about a changed host key with this option.

I can add that maybe as a security option to the settings menu in the future update, would that be ok?

@crschnick
Copy link
Contributor

In the latest release there is now an option to control this behavior. If you disable it, it will no longer pass accept-new

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

No branches or pull requests

2 participants