Keystroke timing obfuscation added to SSH(1)

Re:Keystroke timing obfuscation added to SSH(1) by autoexec on Tuesday August 29, 2023 @02:32PM (#37311945)

WFH also means Working From my backyard, the coffee shop around the corner, the library, a friend's house, a hotel room, etc.

Even for people who only work at home while working remotely, private homes can see a lot of traffic. I wouldn't assume all screens are kept and used in totally secure environments so we should probably still stick with masked passwords and telling users not to keep passwords written on a post-it note stuck to their monitor.

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by aeternum on Tuesday August 29, 2023 @11:40PM (#37317388)

And now employees simply leave their laptop open with the SSH window up while getting their coffee because it's now so annoying to close the lid and correctly type the password.

>USB Rubber Ducky has entered the chat

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by matt-attack on Wednesday August 30, 2023 @10:14AM (#37322478)

If they can see the screen wouldn’t they be better off just looking at the keyboard to directly observe what’s being typed?

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by jgalt212 on Thursday August 31, 2023 @09:53AM (#37337188)

> the coffee shop around the corner

I would hope people in high leverage job roles would just avoid such behavior.

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by froggit on Thursday August 31, 2023 @08:28PM (#37345321)

> I would hope people in high leverage job roles would just avoid such behavior.

I used to hope that as well. Then I met people and lost that hope. It's truly impressive how much stupid shit gets pulled by people that "should know better."

[ Parent | on HN ]