Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Earl A Ramirez
On Fri, 2015-02-13 at 18:27 -0800, PatrickD Garvey wrote: > On Fri, Feb 13, 2015 at 7:12 AM, Lamar Owen wrote: > > On 02/13/2015 05:41 AM, James Hogarth wrote: > > > > This is also why the Orange Book and its Rainbow kin exist (Orange Book = > > 5200.28-STD, aka DoD Trusted Computer System Evaluat

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread PatrickD Garvey
On Fri, Feb 13, 2015 at 7:12 AM, Lamar Owen wrote: > On 02/13/2015 05:41 AM, James Hogarth wrote: > > This is also why the Orange Book and its Rainbow kin exist (Orange Book = > 5200.28-STD, aka DoD Trusted Computer System Evaluation Criteria). > Should anyone care to learn from the Rainbow Books

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Always Learning
On Fri, 2015-02-13 at 11:21 -0500, m.r...@5-cent.us wrote: > I disagree - I am in the "waste of time" camp. The reality is that only > script kiddies start out by trying 22 (and I *do* mean script kiddies - > I've seen attempts to ssh in that were obviously from warez, man, where > they were too

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Always Learning
On Fri, 2015-02-13 at 10:03 -0600, Valeri Galtsev wrote: > On Fri, February 13, 2015 9:05 am, Always Learning wrote: > > I always change the SSH port to something conspicuously different. Every > > server has a different and difficult to guess SSH port number with > > access restricted to a few

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Warren Young
> On Feb 13, 2015, at 9:03 AM, Valeri Galtsev wrote: > > ...changing port numbers...does not really add security. Security through > obscurity is only considered to be efficient by Windows folks. “Security through obscurity” is an overused mantra of derision. Originally, it was a cry against sy

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread m . roth
Always Learning wrote: > > On Fri, 2015-02-13 at 09:46 -0500, Lamar Owen wrote: > >> On 02/13/2015 09:15 AM, Chris Adams wrote: >> > Yeah, the old "move stuff to alternate ports" thing is largely a waste >> > of time and just makes it more difficult for legitimate use. With >> > large bot networks

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Valeri Galtsev
On Fri, February 13, 2015 9:05 am, Always Learning wrote: > > On Fri, 2015-02-13 at 09:46 -0500, Lamar Owen wrote: > >> On 02/13/2015 09:15 AM, Chris Adams wrote: >> > Yeah, the old "move stuff to alternate ports" thing is largely a waste >> > of time and just makes it more difficult for legitimat

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Lamar Owen
On 02/13/2015 05:41 AM, James Hogarth wrote: This is horrible advice anyway. It's not a good idea to run SSH on a port greater than 1024 since if a crash exploit is used to kill the process a non-root trojan process faking SSH to gather credentials could then bind on that port trivially totally c

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Always Learning
On Fri, 2015-02-13 at 09:46 -0500, Lamar Owen wrote: > On 02/13/2015 09:15 AM, Chris Adams wrote: > > Yeah, the old "move stuff to alternate ports" thing is largely a waste > > of time and just makes it more difficult for legitimate use. With > > large bot networks and tools like zmap, finding

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Lamar Owen
On 02/13/2015 09:15 AM, Chris Adams wrote: Yeah, the old "move stuff to alternate ports" thing is largely a waste of time and just makes it more difficult for legitimate use. With large bot networks and tools like zmap, finding services on alternate ports is not that hard for the "bad guys".

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Chris Adams
Once upon a time, James Hogarth said: > If you really want to SSH to a port other than 22 for a little obscurity > use an iptables dnat to map the high port to local host 22 and block 22 > from external connections. Yeah, the old "move stuff to alternate ports" thing is largely a waste of time an

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread James Hogarth
> On 12/02/15 20:03, Warren Young wrote: > > Hi, just a quick note to whoever is maintaining this page: > > > > http://wiki.centos.org/HowTos/Network/SecuringSSH > > > > The procedure is missing the firewall-cmd calls necessary in EL7: > > > > firewall-cmd --add-port 2345/tcp > > firewall-cmd

Re: [CentOS] Securing SSH wiki article outdated

2015-02-13 Thread Ned Slider
On 12/02/15 20:03, Warren Young wrote: > Hi, just a quick note to whoever is maintaining this page: > > http://wiki.centos.org/HowTos/Network/SecuringSSH > > The procedure is missing the firewall-cmd calls necessary in EL7: > > firewall-cmd --add-port 2345/tcp > firewall-cmd --add-port 2

Re: [CentOS] Securing SSH wiki article outdated

2015-02-12 Thread m . roth
Warren Young wrote: > Hi, just a quick note to whoever is maintaining this page: > > http://wiki.centos.org/HowTos/Network/SecuringSSH > > The procedure is missing the firewall-cmd calls necessary in EL7: > > firewall-cmd --add-port 2345/tcp > firewall-cmd --add-port 2345/tcp --permanent > >

[CentOS] Securing SSH wiki article outdated

2015-02-12 Thread Warren Young
Hi, just a quick note to whoever is maintaining this page: http://wiki.centos.org/HowTos/Network/SecuringSSH The procedure is missing the firewall-cmd calls necessary in EL7: firewall-cmd --add-port 2345/tcp firewall-cmd --add-port 2345/tcp --permanent Also, it may be worth mentioning tha