When I use a connection entry such as AnyConnect VPN, RDM will open an interactive CMD shell and inject the necessary keystrokes into the ACTIVE window. Unfortunately, sometimes the user interferes with the automatic process and will activate another programs window while waiting for the VPN entry to finish it's process. This is most prevalent when you need to add certain amounts of delays for the connection process to happen successfully (close existing processes first, delay, open new cmd shell, delay, etc). Ultimately what this tends to lead to is the wrong active window receiving the keystrokes which contain credentials. For example, the keystrokes could be inadvertently typed into an active chat window AND automatically sent to whomever you were corresponding. This has actually happened to me several times, and credentials have accidently been sent into general channels.
What I would like to see is if either of the following are possible:
1) Only ever allow keystrokes to be typed into the intended process, either by process ID, name or window title, rather than just whatever is the current active window.
2) Some sort of process for not ever allowing keystrokes to be typed into an active window listed on a admin/user provided blacklist.
Hello,
I do believe this is the normal behavior but I am unsure if there's anything that can be done to prevent that. I will have to check with the engineering department.
Best regards,
Etienne Lord
Hello,
As Etienne mentionned, this is currently the expected behavior and has been the case for years. That being the case, the ideas you mention seem possible, and I think they would be a great improvement to how macros work in RDM.
I have opened a feature ticket and we will get back to you here once we have an update.
Regards,
Hubert Mireault
Thanks Hubert!
Ya I figured this more along the lines of a feature request. It took me years of dealing with it to finally come create a post about it 😉.