Date: Mon, 21 Nov 2005 11:10:07 +0100 From: Marian Hettwer <MH@kernel32.de> To: Bitbucket <bitbuvket@dannysplace.net> Cc: freebsd-security@freebsd.org, ray@redshift.com Subject: Re: Need urgent help regarding security Message-ID: <43819CFF.7010608@kernel32.de> In-Reply-To: <003201c5ee82$920aaee0$6501a8c0@llama> References: <3.0.1.32.20051117232057.00a96750@pop.redshift.com><43818643.5000206@kernel32.de><20051121085221.GA4267@cirb503493.alcatel.com.au> <43819049.5090107@kernel32.de> <003201c5ee82$920aaee0$6501a8c0@llama>
next in thread | previous in thread | raw e-mail | index | archive | help
Hej there, Bitbucket wrote: > > I agree that this is not good security. It does NOT make your system more > secure. ack :) > But I stop should of saying it should not be done as I can see no > detremental effect to changing the port number. If it makes you sleep > better at night then do it. It cannot hurt. Just dont RELY on it. > Well, it wouldn't make me sleep better at nights, since I know that there's an unpatched sshd out there. And even if it would be on another port, a non-Script-Kiddy could break in easily. Apart from avoiding security by obscurity, you're right, you can do it. If I'm responsible for several dozen of boxes out there, I still couldn't sleep at night, even though the sshd might be on another port than 22 :) Perhaps it winds down to: Do it on your private box, don't do it "at work" :) regards, Marian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43819CFF.7010608>