Hi Scott, a way you can monitor SSH brute force attacks on valid user accounts
is to do something like this:
Step 1: become root / super user
$ su - root
Step 2: edit the /etc/default/login file with your favorite editor and make
sure that SYSLOG=YES is uncommented.
# vi /etc/default/
I ended up changing the SSH port to a non-standard port; this reduced such
attacks to nearly 0.
On Fri, Jul 31, 2009 at 11:54 AM, Tim Evans wrote:
> Take a look at denyhosts (http://denyhosts.sourceforge.net/)
> --
> This message posted from opensolaris.org
>
Take a look at denyhosts (http://denyhosts.sourceforge.net/)
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
I just posted this to that board. Sorry, I did not realize those other boards
were outside of the OpenSolaris board. This post can be deleted on this board.
I could not find a way to move or remove this post. Thanks.
--
This message posted from opensolaris.org
___
Scott:
This seems a better question for security-disc...@opensolaris.org.
Brian
I have recently setup OpenSolaris to use as a file server (I like ZFS) and I connect to this server remotely using SSH. In the past I used iptable rules on Linux to limit connection attempts to SSH within 60 secon
I have recently setup OpenSolaris to use as a file server (I like ZFS) and I
connect to this server remotely using SSH. In the past I used iptable rules on
Linux to limit connection attempts to SSH within 60 seconds to 4 attempts.
This eliminated the Brute Force attempts at guessing userids an
