You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used use a Mac to connect to a Win10 Box. I use the Win10 box as a jumper to other machine e.g. using putty to ssh into other box.
on the putty I often get the "unbound key" message. This is coming from the nano editor in the ssh terminal, but actually I never saw this.
Then sometimes the systems systems to detect a shortcut, so suddently the "Edge Browser" opens and open a couple of times the "office login page".
Actually the remote box has a "Sophos FW" Solution but IT-Services said, it should be deactivated.
You have the "Keyboard Mode"-Button, anyway I do not understand what are the various options and which setup is the one I need ?
How to Reproduce
login on the box
Expected Behavior
keyboard should work
Operating system(s) on local side and remote side
OSX > Win10
RustDesk Version(s) on local side and remote side
1.2.0 > 1.2.0.0
Screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Bug Description
I used use a Mac to connect to a Win10 Box. I use the Win10 box as a jumper to other machine e.g. using putty to ssh into other box.
on the putty I often get the "unbound key" message. This is coming from the nano editor in the ssh terminal, but actually I never saw this.
Then sometimes the systems systems to detect a shortcut, so suddently the "Edge Browser" opens and open a couple of times the "office login page".
Actually the remote box has a "Sophos FW" Solution but IT-Services said, it should be deactivated.
You have the "Keyboard Mode"-Button, anyway I do not understand what are the various options and which setup is the one I need ?
How to Reproduce
login on the box
Expected Behavior
keyboard should work
Operating system(s) on local side and remote side
OSX > Win10
RustDesk Version(s) on local side and remote side
1.2.0 > 1.2.0.0
Screenshots
Additional Context
No response
The text was updated successfully, but these errors were encountered: