SSH tunnel passwords are passed to plink unescaped

Protected posted 4 years ago in Creating a connection
This took me a while to figure out. Passwords with characters that have special meaning in a command line, for example ", must have those characters escaped in the password field itself or they will mess up the plink command. Shouldn't Heidi escape the field before using it?
ansgar posted 4 years ago
Since r4009, the SSH password can contain spaces (see issue #2667). But especially double quotes are still a problem I guess. I'm just not sure how to escape these properly.

This article tells about using the backslash but also other escape chars. I guess we should check the backslash in front of double quotes, or what do you think?

Please login to leave a reply, or register at first.