News for hackers. Stuff that matters.
Re:Ditching Obsidian and building my own by jauntywundrkind on Sunday May 18, 2025 @02:32PM (#44023387)
Ssh exposed on a non-standard port, with root disabled, using key-based auth should be pretty non-controversial.

The security through obscurity (non-standard port, no root) are both kinda silly but why not.

That said, with awesome services like TailScale, it's pretty hard to get locked out of your network. TailScale is so so good at "just working".

Re:Ditching Obsidian and building my own by batch12 on Sunday May 18, 2025 @03:39PM (#44023816)
> The security through obscurity (non-standard port, no root) are both kinda silly but why not

I think these are decent controls when layered with others. The effectiveness differs depending on your threat models, of course, but at the very least it helps reduce the noise seen from most automated scans reducing the effort involved in monitoring your assets.

Re:Ditching Obsidian and building my own by accrual on Sunday May 18, 2025 @03:29PM (#44023763)
Fail2ban or rate-limiting SSH into a block table are useful layers to have as well.
Re:Ditching Obsidian and building my own by cyberax on Sunday May 18, 2025 @03:54PM (#44023914)
Another option is port knocking. Super easy to set up and with 4 knocks it provides 64 bits of randomness.
Re:Ditching Obsidian and building my own by johnmaguire on Sunday May 18, 2025 @05:13PM (#44024355)
Disabling root provides more than security-through-obscurity if your sudo config requires a password to elevate: it essentially means you need both your SSH private key and your password to gain root.