I have solved it partialy by invoking the first command "ssh user@host" in a shell script. Using autotype to run the script, and then typing the password.
But, creating a script for each server I'm connecting to is not practical. So I would like to solve the autotype @ to bash issue.
Any ideas?
Last edit: L1512191 2016-08-12
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The bash console window is not compatible with Two-channel auto-type obfuscation (TCATO). Although, it seems unlikely that this could be the cause of your difficulty, because auto-type disruption caused by TCATO incompatiblity is usually more severe than just dropping a single character.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm trying to autotype ssh login, using bash in Windows 10 v1607 with KeePass v2.x
It works in notepad and CMD but for some reason, the @ is not being typed in bash.
String = ssh{USERNAME}@{URL}{ENTER}{PASSWORD}{ENTER}
or if you're lazy:
String = {WIN}run{ENTER}{DELAY 500}bash{ENTER}{DELAY 500}ssh{USERNAME}@{URL}{ENTER}{PASSWORD}{ENTER}
I have solved it partialy by invoking the first command "ssh user@host" in a shell script. Using autotype to run the script, and then typing the password.
But, creating a script for each server I'm connecting to is not practical. So I would like to solve the autotype @ to bash issue.
Any ideas?
Last edit: L1512191 2016-08-12
In the Windows bash console on Windows 10 v1607 using KeePass 2.34
I can auto-type a keystroke sequence such as
where:
USERNAME is a value such as wellread1
URL is a domain_name
It appears in the bash console as:
Last edit: wellread1 2016-08-12
The bash console window is not compatible with Two-channel auto-type obfuscation (TCATO). Although, it seems unlikely that this could be the cause of your difficulty, because auto-type disruption caused by TCATO incompatiblity is usually more severe than just dropping a single character.
Updated from v2.28 to v2.34 solved it. Thanks =)