I love the idea of Single-Packet Authorization with fwknop instead of port knocking: http://www.cipherdyne.org/fwknop/
Re:What SSH Hacking Attempts Look Like
by AlexCoventry on Saturday May 05, 2018 @09:57PM
(#17004916)
How does fwknop compare to knockknock? https://moxie.org/software/knockknock/
Re:What SSH Hacking Attempts Look Like
by michaelrash on Sunday May 06, 2018 @08:09PM
(#17009437)
The design decisions that govern fwknop provide guidance on how fwknop is different from knockknock: http://www.cipherdyne.org/fwknop/docs/fwknop-tutorial.html#d...
Re:What SSH Hacking Attempts Look Like
by AlexCoventry on Monday May 07, 2018 @11:36AM
(#17013551)
Thanks.
I wish fwknop would be added to pfsense.
Nothing wrong with this, but a strong password for all Unix accounts (or, ideally, only allowing SSH with public key authentication) is essentially all you need. Unless you're using a dumb password, you're far more likely to be compromised by an application or OPSEC flaw (like someone getting into the email you used to register your server hosting account) than some crazy SSH compromise.
Curious, what specifically does nftables offer in this context that iptables doesn't ?
why nftables rather than iptables?
Im also curious about this, they use the same netfilter backend
Re:What SSH Hacking Attempts Look Like
by arca_vorago on Tuesday May 08, 2018 @09:40AM
(#17020788)
Just looking toward the future. I think bpf is cool but not aimed at production routing that most network techs can approach. nftables fixes so many issues of iptables and is generally viewed as it's replacement. nftables also has a smaller attack surface due to its youth mostly.
So I made the choice to go ahead and focus on learning nft. It's been enjoyable.
Is that true? I thought nftables was still behind on supported features compared to iptables and nftables runs on a VM.
Anyway, nftables should be nicer to administer. More pf-like.
IP whitelist is tough when your home network has a dynamic IP.
Re:What SSH Hacking Attempts Look Like
by purple-again on Saturday May 05, 2018 @09:58AM
(#17001806)
I called up my provider and paid a little extra for a fixed IP. Really it was just laziness though because in practice my home IP seemed to only change when I restarted the router.
IP-Range would stay relatively similar.
3... 89... 92... very occasionally 118... or 184...
TalkTalk UK, jumps around a lot; YMMV.
Last octet or first?
nftables instead of iptables
port-knocking
non-standard port
key+pass access/auth
ip whitelist
good logging
ED25519 wherever possible!!!