Details
-
Bug
-
Resolution: Fixed
-
Low
-
4.3.2
Description
Steps to reproduce
- Add an SSH Task to a job.
- Add a server that does have sshd running on port 22, choose a custom port number other than 22, but ensure otherwise the authentication details are correct.
- Run the plan.
- Notice that the SSH task runs successfully, despite the custom port being set to one that sshd is not listening on.