Re: [tlug] server installation best practices/ worksheet

["Erin D. Hughes" <erin-hughes@example.com>]

Brett Robson wrote:
> Godwin Stewart wrote:
> > I run several servers open to the public. All of them have had sshd
> > listening to a non-standard port ever since I started adminning them,
> > and that was 3 or 4 years ago. I have yet to see a single attack on
> > sshd on that non-standard port. So, while nmap can indeed make a good
> > guess at what service is running on a given port, I see no evidence of
> > attackers actually using that feature. Maybe it'll come later, I don't
> > know, but for the time being I have no reason whatoever to run sshd on
> > port 22 on any of my boxen.
> >
> >   
>
>
> I do that too, I'm the only one who should be attaching to my machine. 
> It certainly keeps your logs a lot cleaner and easy to read.
I second that notion and just cause it is a non-standard port does not 
mean your company documentation can not cover it. Non-standard for 
everyone else doesn't mean non-standard for you. Documentation is the 
key. Probably should have mentioned that in my post.

> I also have this in my /etc/hosts.deny
> ALL: .tw, .cn, .hk, .kr, .pk, .th
I am not too keen on /etc/hosts.deny but to each his own.

E./

--
Erin D. Hughes 
GMO Internet,