-
Notifications
You must be signed in to change notification settings - Fork 235
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
Allow SSH on non-standard ports #275
Comments
What scripts do you mean? |
Sorry for the late response. Currently I am developing a Inspec Profile for compliance. My requirement is , to test the SSH daemon is available on a Linux machine but not via the default port (22):
Here the compliance test fails. So, if I will able to specify the port then I think it will help a lot. |
Testing anything involving sshd is unfortunately out of scope for kitchen-docker just as a side effect of how it works. Any tests would be a false positive. This could be improved in the future, but it doesn't seem likely given the limitation of distro packages (i.e. it isn't just the port that collides, it's all the config files too). |
Seems the driver is hardcoded to start the SSHd service on port 22, but it's really very useful to allow SSH on non-standard ports so we can test various automation scripts those have different requirements. It will take a little amount of effort to update.
The text was updated successfully, but these errors were encountered: