Actually this bug was not fixed until 2018.06!
Anyway, the problem you are seeing should be easy to work around by creating a private SSH key in the indicated directory and use that instead of the username/password method to connect to the remote machine.