News for hackers. Stuff that matters.
Re:Why Putting SSH On Another Port is a Good Idea by derefr on Friday October 25, 2013 @11:35PM (#6616176)
The ability for someone to "spin up a daemon on your server" would also be called an unprivileged exploit. The ability to spin up a daemon on port 22 on your server, however, would be called a privilege-escalation exploit waiting to happen.

If a zero-day gets discovered in the kernel that allows the former, you'll be hoping that it isn't also the latter. This is why trusting unprivileged ports is a bad idea.

(...until, you know, we finally start using DNS service-records for this sort of thing.)

Re:Why Putting SSH On Another Port is a Good Idea by GalacticDomin8r on Saturday October 26, 2013 @01:09AM (#6616433)
> The ability for someone to "spin up a daemon on your server" would also be called an unprivileged exploit.

No, that is very, very wrong. This is SOP for an account on a system

nc -l 9000 <- spinning up a daemon on your server

Re:Why Putting SSH On Another Port is a Good Idea by derefr on Saturday October 26, 2013 @12:09PM (#6617857)
Rather, the ability for someone who isn't considered to have an account on your server, to spin up a daemon on your server.