search for: obscurekeystroketim

On Wed, 6 Sep 2023, procmem at riseup.net wrote: > Hi, Whonix OS privacy dev here. I had a discussion concerning the new > ObscureKeystrokeTiming feature with a prominent researcher and author of the > mouse and keyboard biometrics obfuscation tool called Kloak. While it's > exciting to see keystroke obfuscation measures [1] start to become more > prevalent mainstream, the current implementation of using a 50Hz fixed packet &...

https://bugzilla.mindrot.org/show_bug.cgi?id=3655 Bug ID: 3655 Summary: Default ObscureKeystrokeTiming makes X forwarding really slow Product: Portable OpenSSH Version: 9.6p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh Assignee: unassigned-b...

...way that led to the delay? >> >> Most likely the cause is an unexpected side effect of some other change. >> There have been some interesting changes to SSH with this release, >> perhaps try disabling: >> >> http://man.openbsd.org/OpenBSD-7.4/ssh_config#ObscureKeystrokeTiming >> >> I would be surprised if this is actually the cause, but it is a change >> that was introduced and something that is easily tested. >> >> You could also look through: >> >> http://www.openbsd.org/plus74.html >> >> See if any of the...

...way that led to the delay? >> >> Most likely the cause is an unexpected side effect of some other change. >> There have been some interesting changes to SSH with this release, >> perhaps try disabling: >> >> http://man.openbsd.org/OpenBSD-7.4/ssh_config#ObscureKeystrokeTiming >> >> I would be surprised if this is actually the cause, but it is a change >> that was introduced and something that is easily tested. >> >> You could also look through: >> >> http://www.openbsd.org/plus74.html >> >> See if any of the...

...rot.org Reporter: chsdik at gmail.com As of OpenSSH 9.6p1, when starting a X11 (ssh -X) application, it takes around 5 seconds before the window finally appears. I have seen this on Solaris but I've seen quite a few reports for Linux and others. This can be worked around by setting ObscureKeyStrokeTiming to no; it appears that the code does not distinguish between actual keys typed in or other data to be send. In the point where we try to obscure the timing, we no longer now where the data comes from. $ ssh -X <host> ... $ time xterm -e true real 0m4.89s user 0m0.05s sys 0m0....

...gt; >> > >> Most likely the cause is an unexpected side effect of some other change. > >> There have been some interesting changes to SSH with this release, > >> perhaps try disabling: > >> > >> http://man.openbsd.org/OpenBSD-7.4/ssh_config#ObscureKeystrokeTiming > >> > >> I would be surprised if this is actually the cause, but it is a change > >> that was introduced and something that is easily tested. > >> > >> You could also look through: > >> > >> http://www.openbsd.org/plus74.html &...

On Wed, 8 Nov 2023, Roger Marsh wrote: > Damien, > > Sorry about distributed context. > > Those discussions told me about the new ObscureKeystrokeTiming > argument to the ssh command. One reply suggested I try that because it > is easy to test. > > Most of my xterm ssh command combinations in fvwm configuration file > are expressed 'Exec exec xterm -title ... -e ssh <user>@<host>' and do > not have a noticab...

...ocket buffer. > Previously it was possible to create a sufficiently large > configuration that could cause sshd to fail to accept any > connection. sshd(8) will now actively manage sending its config > to the sshd-session sub-process. > > * ssh(1): don't start the ObscureKeystrokeTiming mitigations if > there has been traffic on a X11 forwarding channel recently. > Should fix X11 forwarding performance problems when this setting > is enabled. bz3655 > > * ssh(1): prohibit the comma character in hostnames accepted, but > allow an underscore as the...

...it in a (possibly enlarged) socket buffer. Previously it was possible to create a sufficiently large configuration that could cause sshd to fail to accept any connection. sshd(8) will now actively manage sending its config to the sshd-session sub-process. * ssh(1): don't start the ObscureKeystrokeTiming mitigations if there has been traffic on a X11 forwarding channel recently. Should fix X11 forwarding performance problems when this setting is enabled. bz3655 * ssh(1): prohibit the comma character in hostnames accepted, but allow an underscore as the first character in a hostname...