Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

PLink and privkey passphrase handling..

jfalch's profile image jfalch posted 7 years ago in General Permalink
it's quite nice that heidsql for some time now has parsed out messages output by plink.exe, and shows these in information dialogs.

it would be even nicer if this treated the message

Passphrase for key "...":

specially, namely by showing an input dialog instead of a message dialog, and passing its input string back to plink.exe's stdin.
ansgar's profile image ansgar posted 7 years ago Permalink
Yes, that's currently output which is somehow unexpected by HeidiSQL's plink integration. I'm not sure if I can get that to work but I'll have a look.
jfalch's profile image jfalch posted 7 years ago Permalink
that would be nice. because of the current behaviour, it is not possible to use encrypted key files with heidisql, which i would prefer to do for security reasons.
NbgRalle's profile image NbgRalle posted 7 years ago Permalink
Not entirely sure if we're having the same problem, but I found this thread via Google, so I'll leave this message here for other people like me.

that would be nice. because of the current behaviour, it is not possible to use encrypted key files with heidisql, which i would prefer to do for security reasons.



It is possible if you enter the passphrase in the SSH password field. If you still get the message from above, your passphrase probably contains one or more double quote characters (") and that does not get escaped, causing the connection attempt to fail. Choose a passphrase without double quotes and it should work. I've opened a thread about this here.

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




Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.