Hacker News new | ask | show | jobs
by pmoriarty 3296 days ago
Why is this a service and not a standalone tool that I can use from my own machine?

Do I really want to be giving out the locations of my ssh servers to some random website?

Also, a standalone tool could be used behind corporate firewalls, where this service is useless.

3 comments

I tried entering my personal server's hostname and port number but it timed out trying to connect. Then I remembered that I configured my server's firewall to only allows SSH connections from my home ISP or work IP address.

I too would prefer to use a standalone tool that I could use for testing my SSH configuration without having to temporarily disable those firewall rules.

Well, yes and no - I can see the argument that it might be nice to test them locally before you expose them to the world (and I suppose you might also have them on a private LAN permanently), but otherwise, they will be tested, by someone, and soon...
But the fewer people "test" it, apart from me, the better.

This is akin to putting your email address all over the internet. If you do that, you're going to get lots of spam. If you are more careful about who you give it to, you'll get less.

It's clearly a win to keep both email addresses and ssh server addresses as private as possible.

The difference between IP and email adresses is that one is trivially enumerated, the other is not.

Any internet-facing server that responds on port 22 will get several (up to hundreds) of failed login attempts per day. Just install something like fail2ban and watch your logs.

When was the last time you looked at your SSH logs for public machines? Your public IP is just that, public. Anyone can scan it, and it most certainly gets hit by many scanners a day.
Yeah I'd like a local tool. Maybe I want to do a test before I put it on the internet.
Not quite the same but there's always

  nmap --script ssh2-enum-algos.nse