Re: Running ssh on unreserved ports

2011-02-21 Thread Anne Wilson
On Sunday 20 February 2011 22:13:16 Patrick Kobly wrote: > On 2011-02-20, at 9:05 AM, "Alex" wrote: > > Hi, > > > >>> Fail2ban is easy to set up, and I've seen it stop attempts here. > > > > Everything helps, but this is one that I wouldn't really rely on, in > > case the log file format for ssh

Re: Running ssh on unreserved ports

2011-02-20 Thread Patrick Kobly
On 2011-02-20, at 9:05 AM, "Alex" wrote: > Hi, > >>> Fail2ban is easy to set up, and I've seen it stop attempts here. > > Everything helps, but this is one that I wouldn't really rely on, in > case the log file format for ssh changed in some way, or the script > died and it wasn't noticed. F

Re: Running ssh on unreserved ports

2011-02-20 Thread Genes MailLists
On 02/20/2011 11:00 AM, Alex wrote: > Hi, > >>> I'd like to move it to a higher port to avoid the normal doorknob >>> rattling that occurs with ssh running on a public server. >> >> Does this work for you (assumign 1234 is what you want to listen on) >> semanage port -a -t ssh_port_t -p tcp 1234

Re: Running ssh on unreserved ports

2011-02-20 Thread Genes MailLists
On 02/20/2011 11:05 AM, Alex wrote: > > I also recently found this: > > # Google Authenticator > http://www.google.com/support/accounts/bin/answer.py?hl=en&answer=1066447 > > This is apparently some application that somehow integrates with your > phone to authenticate you with ssh? Anyone have

Re: Running ssh on unreserved ports

2011-02-20 Thread Alex
Hi, >> Fail2ban is easy to set up, and I've seen it stop attempts here. Everything helps, but this is one that I wouldn't really rely on, in case the log file format for ssh changed in some way, or the script died and it wasn't noticed. > I am paranoid about ssh and welcome suggestions that incr

Re: Running ssh on unreserved ports

2011-02-20 Thread Alex
Hi, >> I'd like to move it to a higher port to avoid the normal doorknob >> rattling that occurs with ssh running on a public server. > >  Does this work for you (assumign 1234 is what you want to listen on) > semanage port -a -t ssh_port_t -p tcp 1234 This worked great, thanks. Alex -- users m

Re: Running ssh on unreserved ports

2011-02-19 Thread Adrian Sevcenco
On 02/19/2011 05:45 PM, Rick Sewill wrote: > On Saturday, February 19, 2011 04:28:11 am Anne Wilson wrote: >> On Saturday 19 February 2011 10:20:30 Tim wrote: >>> On Fri, 2011-02-18 at 16:07 -0500, Alex wrote: I'd like to move it to a higher port to avoid the normal doorknob rattling that

Re: Running ssh on unreserved ports

2011-02-19 Thread James McKenzie
On 2/19/11 8:45 AM, Rick Sewill wrote: > On Saturday, February 19, 2011 04:28:11 am Anne Wilson wrote: >> On Saturday 19 February 2011 10:20:30 Tim wrote: >>> On Fri, 2011-02-18 at 16:07 -0500, Alex wrote: I'd like to move it to a higher port to avoid the normal doorknob rattling that occ

Re: Running ssh on unreserved ports

2011-02-19 Thread Rick Sewill
On Saturday, February 19, 2011 04:28:11 am Anne Wilson wrote: > On Saturday 19 February 2011 10:20:30 Tim wrote: > > On Fri, 2011-02-18 at 16:07 -0500, Alex wrote: > > > I'd like to move it to a higher port to avoid the normal doorknob > > > rattling that occurs with ssh running on a public server.

Re: Running ssh on unreserved ports

2011-02-19 Thread Anne Wilson
On Saturday 19 February 2011 10:20:30 Tim wrote: > On Fri, 2011-02-18 at 16:07 -0500, Alex wrote: > > I'd like to move it to a higher port to avoid the normal doorknob > > rattling that occurs with ssh running on a public server. > > Even with it on a different port, you'd probably want to impleme

Re: Running ssh on unreserved ports

2011-02-19 Thread Tim
On Fri, 2011-02-18 at 16:07 -0500, Alex wrote: > I'd like to move it to a higher port to avoid the normal doorknob > rattling that occurs with ssh running on a public server. Even with it on a different port, you'd probably want to implement some firewalling that auto-bans an IP after few failed a

Re: Running ssh on unreserved ports

2011-02-18 Thread Alex
Hi, >> I'd like to move it to a higher port to avoid the normal doorknob >> rattling that occurs with ssh running on a public server. > You can do this from iptables: > > 1. block port 22 in iptables > > 2. Add the following rule: >   iptables -t nat -A PREROUTING -p tcp -m tcp --dport 2345 -m sta

Re: Running ssh on unreserved ports

2011-02-18 Thread Alex
Hi, >> I'd like to move it to a higher port to avoid the normal doorknob >> rattling that occurs with ssh running on a public server. > >  Does this work for you (assumign 1234 is what you want to listen on) > > semanage port -a -t ssh_port_t -p tcp 1234 Great, thanks, I'll try that tonight. That

Re: Running ssh on unreserved ports

2011-02-18 Thread Gabriel VLASIU
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 18 Feb 2011, Alex wrote: > I'd like to run an ssh server as root on a port greater than 1024 > instead of the normal 22 but selinux doesn't seem to like that. How > can I get around that? > > I'd like to move it to a higher port to avoid the

Re: Running ssh on unreserved ports

2011-02-18 Thread Genes MailLists
On 02/18/2011 04:07 PM, Alex wrote: > Hi, > > I'd like to run an ssh server as root on a port greater than 1024 > instead of the normal 22 but selinux doesn't seem to like that. How > can I get around that? > > I'd like to move it to a higher port to avoid the normal doorknob > rattling that occu

Running ssh on unreserved ports

2011-02-18 Thread Alex
Hi, I'd like to run an ssh server as root on a port greater than 1024 instead of the normal 22 but selinux doesn't seem to like that. How can I get around that? I'd like to move it to a higher port to avoid the normal doorknob rattling that occurs with ssh running on a public server. Thanks, Ale