Open tezla2018 opened 4 years ago
I was seeing this in the 2.3.1 release and continue to see it in the 2.3.3. I can provide Debug logging, just not sure which Debug level is best to use. I've already got a set of Debug2 logs from both server and client.
@tezla2018 Were you switching back to Firefox by chance when you went back to the server machine? I've been playing around with this, and it seems like whenever Firefox is the active app on the server, the client's keystrokes are randomized. If I make another application the active app and move back to the client, the keystrokes are normal.
I tested with FF, Chrome, and Edge; only FF seems to exhibit this behavior in my testing.
@tyborg-GM it didn't matter what app was on the server for me actually. I tested with chrome, notepad, notepad ++, your phone app. And I actually don't have firefox installed on either machine. That's interesting though you get the same behavior with FF. Does it happen at all when you don't use FF?
Operating Systems
Server: Windows 10 Pro 1909
Client: Windows 10 Pro 1909
Barrier Version
Barrier Version 2.3.3 on both
Steps to reproduce bug
Other info
Just started happening after updating from 2.3.2 to 2.3.3. I have not changed any settings. Random Keystrokes on client does not happen if I do not type on server. IE if I move cursor from client to server back to client no issue occurs, only when any key is hit on server then try to type on client. Current workaround is a reload or stop start of Barrier but will happen every time I type on the server EDIT Does this bug prevent you from using Barrier entirely? YES
I haven't been able to figure out how to properly log things, every time I try to save anything to the log it never shows up. Any thoughts would be much appreciated.
UPDATE: I discovered after messing around with everything that if I disable SSL on both server and client and reload, everything works as intended. I then re-enabled SSL and the issue came back. The SSL Fingerprints did not match... not sure if they are supposed to.
UPDATE2: Looks like SSL wasn't the issue seems to be random now...