You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Securing OpenSSH Server [Part 1]:

#16 Re: Securing OpenSSH Server [Part 1] Posted by Anonymous (80.237.xx.xx) on Thu 10 Jan 2008 at 19:54 Actually I find it to be quite the panacea. Simple to implement, and in the years since I've done it I've not gotten even 1 attempt. These are bots, and they do not search for the new port. It's really not worth it to do so. I generally find that 22 is not considered a standard port, but for that I have a system setup to do ssh tunnels over port 80. The QoS issue is interesting, but I've never come across it in the US. And I'd probably be fine with lag in return for the freeing the resources consumed by trying to deal with these login attempts. My advice would be to try changing the port first, and only if you find that to be unacceptable is it worth investigating other options.

Username:	Anonymous
Title:
Your Comment:
Posting Format:	BBCode HTML Text Plain Text Textile

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account