News for hackers. Stuff that matters.

A comment on What SSH Hacking Attempts Look Like. Parent comment

Re:What SSH Hacking Attempts Look Like by s3m4j on Saturday May 05, 2018 @08:44AM (#17001579)
A port knock is just a clear password :/

I much prefer restricting port 22 to a few ip and disable passwords

[ Parent | on HN ]
Re:What SSH Hacking Attempts Look Like by lakechfoma on Saturday May 05, 2018 @09:32AM (#17001714)
Not with single packet authentication from fwknop

http://www.cipherdyne.org/fwknop/docs/fwknop-tutorial.html#w...

[ Parent | on HN ]
Re:What SSH Hacking Attempts Look Like by Operyl on Saturday May 05, 2018 @09:35AM (#17001727)
fwknop has a cache to prevent replay attacks, that plus the fact the packets are only valid for a certain length of time pretty much thwarts this. Remember, fwknop is _in addition_ to your existing security practices, it is not the only "password."
[ Parent | on HN ]
Re:What SSH Hacking Attempts Look Like by rsync on Saturday May 05, 2018 @02:36PM (#17003115)
"A port knock is just a clear password"

It is only clear to the routers in your traceroute ... third party attackers cannot snoop on this traffic.

[ Parent | on HN ]
Re:What SSH Hacking Attempts Look Like by sliken on Saturday May 05, 2018 @07:35PM (#17004466)
Right, exactly like a clear text password.
[ Parent | on HN ]