Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

possible hacking?



On Wed, Jan 25, 2006 at 10:55:29AM -0500, Kent Borg wrote:
> On Wed, Jan 25, 2006 at 08:49:40AM -0500, Ward Vandewege wrote:
> > On Wed, Jan 25, 2006 at 08:36:07AM -0500, Rich Braun wrote:
> > > I also have discovered there is more "security in obscurity" than many
> > > experts think. By moving sshd to a high-numbered port (instead of 22) I
> > > see no break-in attempts at all on my system--over a period of
> > > years--vs the more-typical several dozen per day if you leave port 22
> > > visible.
> > 
> > Yes, same observation here. But this might only be a matter of time.
> 
> At a former job we had an unmaintained Linux machine with ssh on a high
> port, and it got cracked.
> 
> On my basement server I have ssh on the regular port, but I use strong
> passwords.

Better yet; disallow direct (root) logins with passwords. Only allow them with
keys.

Ward.

-- 
Pong.be         -(   "If you think penguins are fat and waddle, you have   )-
Virtual hosting -( never been attacked by one running at you in excess of  )-
http://pong.be  -(                   100 MPH." -- Linus                    )-
GnuPG public key: http://gpg.dtype.org




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org