Changing SSH Port from 22 to something makes a difference :) i had once set it to default 22, and 100 attacks from china, brazil, italy daily... i tried changing it to XXXX and it all goes to ZERO :)
so the first step is to change SSH port and it will help a lot, then do the other necessary steps mentioned. On 7/29/05, Holden Hao <[EMAIL PROTECTED]> wrote: > My recommended SSh best practices would be: > > > - Move SSH to listen to another port just to stop scripted attempts > > - Disallow root log-ins > > - Only allow certain users to log-in > > - Enforce use of host-based authentication > > - Use Private-Public Key Authentication and disable Password Authentication > > - Disable port tunneling for some users > > - Use the "command" attribute in authorized_keys to limit what an SSh > connection can do > > > Holden > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > [email protected] (#PLUG @ irc.free.net.ph) > Read the Guidelines: http://linux.org.ph/lists > Searchable Archives: http://archives.free.net.ph > -- "mailing lists is my personal knowledgebase" _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
