New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
password downshift problem #742
Comments
Hey @McThump, Thanks for reporting this issue! It seems like the remote access software is not passing the SHIFT events. What software are you using for remote access? Cheers :) |
Hi @federico-terzi, Yes. When I manually enter passwords using the keyboard there is no problem, but when they are inserted by Espanso the shift is not preserved. I am using AnyDesk and Remmina (for RDP connections) on Ubuntu for remote access and it happens with both of them. I tested this with Espanso on Windows 10 using the native Windows RDP client to remote to another Windows host. In this case, the shift is preserved and the problem does not occur. |
@McThump Interesting, thank you. Does this problem happen also with other applications in the same remote session? I mean, I understand that you can't login because of this problem, but can you expand correctly on other applications inside the remote host? |
@federico-terzi - Ah, excellent question! Yes, the problem occurs for all apps! So far, I had only been using it for password entry. |
@McThump I see, thank you! We'll investigate :) |
@federico-terzi, @McThump: I'm not sure exactly why this is happening, but I too had a similar problem and found a work-around. I'm using a QEMU/KVM host (Pop!-OS 21.04) and run both Windows 10 and Windows 7 guests that leverage SPICE/QXL for displays and am using both More specifically, if I were to have a bit of text like: Thus, all "shift+character" keystrokes are converted to simply "character" ones. Before using espanso, I used another utility for typing text in Linux hosts: - trigger: ":my_pw"
replace: "{{output}}"
vars:
- name: output
type: shell
params:
cmd: "xdotool type 'ThIsIsCoMpLiCaTeD!,>@;"'"
trim: false results in a successful expansion of As an aside, a reddit post led me to search for this issue in the repo. Cross-posting in case anyone else follows the same path I did. |
@jtmackoy Interesting! Thank you for sharing, this might be helpful to find a solution |
Hey guys! I've investigated a bit on this issue. I think we'll probably need to create a few custom patches for these RDP apps, as I recently did for VirtualBox (see 8bab0f5#diff-e74564942afd14440713086d293920c28915cafe7578356232337b6c4d102415) When you have the chance, could you please post here the detect information about your problematic clients? Here's a quick guide on how to get that information: https://espanso.org/docs/configuration/#finding-the-right-filters With your help, we can bundle these edge cases into the new v2 version, so that hopefully this will work out-of-the-box :) |
Hey @federico-terzi! Sorry for the delay, here's the info on the client I'm using for this issue, with some personal info
Interestingly, the
Hope this helps with your filter work. BTW, just tried the the 2.1.1-alpha version and my workaround broke there. |
@jtmackoy Thanks! Sorry for the late reply
Could you please try adding a filter_class: "Remote-viewer"
backend: Inject
key_delay: 10
inject_delay: 15
disable_x11_fast_inject: true And see if that helps? If that works, we can integrate the patch into Espanso itself Cheers :) |
Being a bit of an issue necromancer here - I was seeing this lowercasing issue while using triggers in vim (either locally or on remote machines via SSH).
|
|
Hi,
I am using Espanso on Linux and created the following to enter complex passwords from the clipboard when remotely accessing Windows computers:
Windows will not allow the pasting of passwords from the clipboard into the login box, but this Espanso match can enter them. The problem is that any uppercase characters in the clipboard are downshifted to lower case. So, for example, a password of "aAbBcC!@" is entered into the Windows password box as "aabbcc12". This problem only occurs for text inserted into password fields. Anywhere else is fine. I connect to these remote machines many times during the day. Getting this to work would be very helpful.
The text was updated successfully, but these errors were encountered: