Keystroke timing obfuscation added to SSH(1)

Re:Keystroke timing obfuscation added to SSH(1) by DisgracePlacard on Tuesday August 29, 2023 @10:54AM (#37308842)

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by suck-my-spez on Tuesday August 29, 2023 @11:19AM (#37309220)

Can’t get on board with a privacy tool if the first thing they ask you to do is to join their Telegram channel

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by predictabl3 on Tuesday August 29, 2023 @03:08PM (#37312381)

Since I'm the one that said it originally, I tend to strongly agree. I really can't stand it. Its such an absolute, unnecessary respect killer.

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by abwizz on Wednesday August 30, 2023 @10:00AM (#37322298)

tend to sympathize, it's slack or discord invites that trigger it for me

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by vngzs on Tuesday August 29, 2023 @11:04AM (#37308993)

So Tor with a blockchain, and you have to pay for it?

> Users pay a fee in NYM to send their data through the mixnet.

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by dmos62 on Tuesday August 29, 2023 @11:16AM (#37309167)

To be fair, Tor costs too, it's just that someone else is picking up the bill.

[ Parent | on HN ]

Re:Keystroke timing obfuscation added to SSH(1) by rendx on Tuesday August 29, 2023 @08:08PM (#37315913)

Tor is not a mixnet, since it cannot delay individual packets or messages, which is a requirement for actual "mixing". Tor is onion routing.

[ Parent | on HN ]