News for hackers. Stuff that matters.
Re:Show HN: Ruroco – like port knocking, but better by gz5 on Friday August 23, 2024 @10:23AM (#41329289)
Nice. The deadline argument concept is smart and not in many other implementations.

It seems there are two sides of the spectrum for secure SSH access:

+ Relatively infrequent access by limited # of people to servers which are not top targets for attacks. Solutions like the one above are great for this.

+ More frequent, more users, more sensitive servers. Close all the inbound ports, permanently. Example: https://github.com/openziti-test-kitchen/zssh (or with an integrated OIDC like KeyCloak - https://youtu.be/NZJtzSoS_g0?si=Qg6p6Hdkaq1ahefg)

Re:Show HN: Ruroco – like port knocking, but better by mschempp on Friday August 23, 2024 @12:17PM (#41330278)
"+ Relatively infrequent access by limited # of people to servers which are not top targets for attacks. Solutions like the one above are great for this."

Thats exactly what I'm using it for - I'm the only one on my server :)

Re:Show HN: Ruroco – like port knocking, but better by mrbluecoat on Friday August 23, 2024 @11:02AM (#41329604)
I agree. Instead of closing port 22 only to open a different port, it seems more secure to close all ports like the zssh example above or Tailscale SSH [1] or SSH No Ports [2].

[1] https://tailscale.com/tailscale-ssh

[2] https://atsign.com/resources/articles/close-port-22-forever-...

Re:Show HN: Ruroco – like port knocking, but better by 0cf8612b2e1e on Friday August 23, 2024 @12:04PM (#41330154)
SSH on something other than port 22 is not more secure, but it does massively reduce the amount of log noise. Which I find invaluable since I do not have a security team monitoring my machines.