Article View: uk.comp.os.linux
Article #454Re: Security
From: Paul Richards
Date: Sun, 12 Dec 1999 00:00
Date: Sun, 12 Dec 1999 00:00
123 lines
5249 bytes
5249 bytes
Steve Dodd wrote:
>
> Paul Richards <pauldoo@dunvegan1.demon.co.uk> wrote:
>
> > I've recently got my Linux (Debian) box set up back to how it was before
> > I broke it. (Well M$ FDISK decided to make a FAT32 partition overlap my
> > EXT2 which was nice when I tried to format the FAT32..) What should I
> > do to make the system more secure? I no longer have dual boot, only
> > Linux because I was pissed off with what M$ FDISK done.
>
> My advice is probably going to sound patronising, but it's not supposed to
> be: basically, get to know your system, and understand how things work.
> When you say you want your system "secure", presumably you mean w.r.t. people
> getting in over the internet, rather than security on the console.
> Look at everything that's listening for connections / packets (netstat -t -u
> -l works for me), decide if you need it running or not. For those that you
> do need running, read the docs, look at any configuration options, etc.
OK here goes:
tcp 0 0 *:4666 *:*
LISTEN
tcp 0 0 *:1239 *:*
LISTEN
tcp 0 0 *:1177 *:*
LISTEN
tcp 0 0 *:1176 *:*
LISTEN
tcp 0 0 *:1175 *:*
LISTEN
tcp 0 0 *:1174 *:*
LISTEN
tcp 0 0 *:1173 *:*
LISTEN
tcp 0 0 *:1172 *:*
LISTEN
tcp 0 0 *:1171 *:*
LISTEN
tcp 0 0 *:1164 *:*
LISTEN
tcp 0 0 *:6000 *:*
LISTEN
tcp 0 0 *:4383 *:*
LISTEN
No idea what those were
tcp 0 0 *:nntp *:*
LISTEN
My NTP server???
tcp 0 0 *:ftp *:*
LISTEN
I need this
tcp 0 0 *:www *:*
LISTEN
And this
tcp 0 0 *:5865 *:*
LISTEN
tcp 0 0 *:55556 *:*
LISTEN
tcp 0 0 *:5556 *:*
LISTEN
tcp 0 0 *:omniorb *:*
LISTEN
tcp 0 0 *:9111 *:*
LISTEN
tcp 0 0 *:803 *:*
LISTEN
No idea
tcp 0 0 *:printer *:*
LISTEN
Do I need this? lpr does the printing AFAIK
tcp 0 0 *:socks *:*
LISTEN
No idea
tcp 0 0 *:auth *:*
LISTEN
Am I a PAP server or something stupid?
tcp 0 0 *:vboxd *:*
LISTEN
tcp 0 0 *:saft *:*
LISTEN
No idea
tcp 0 0 *:finger *:*
LISTEN
I know this one, but DoS attacks can come from this right?
tcp 0 0 *:smtp *:*
LISTEN
tcp 0 0 *:pop3 *:*
LISTEN
I need those two, but perhaps I could place IP restrictions... ?
tcp 0 0 *:telnet *:*
LISTEN
Need this
tcp 0 0 *:time *:*
LISTEN
Or is this my NTP server???
tcp 0 0 *:daytime *:*
LISTEN
tcp 0 0 *:discard *:*
LISTEN
tcp 0 0 *:sunrpc *:*
LISTEN
No idea what those were
OK chaps, enlighten me.
--
Paul Richards (Pauldoo) - http://www.pauldoo.co.uk
I've not ran any Microsoft code for 1351078 seconds.
How about you?
Technical Details
Message-ID:
<38539997.AE21B515@dunvegan1.demon.co.uk>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<38513A2C.F927313@dunvegan1.demon.co.uk> <8302l8$hbd$1@falstaff.loth.demon.co.uk>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10d8ad,f54179a9240e5606 X-Google-Attributes: gid10d8ad,public X-Google-Thread: fac57,f54179a9240e5606 X-Google-Attributes: gidfac57,public From: Paul Richards <pauldoo@dunvegan1.demon.co.uk> Subject: Re: Security Date: 1999/12/12 Message-ID: <38539997.AE21B515@dunvegan1.demon.co.uk> X-Deja-AN: 559718451 Content-Transfer-Encoding: 7bit X-NNTP-Posting-Host: dunvegan1.demon.co.uk:193.237.111.243 References: <38513A2C.F927313@dunvegan1.demon.co.uk> <8302l8$hbd$1@falstaff.loth.demon.co.uk> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@demon.net X-Trace: news.demon.co.uk 945012559 nnrp-14:617 NO-IDENT dunvegan1.demon.co.uk:193.237.111.243 Organization: Pauldoo's Linux Box Mime-Version: 1.0 Newsgroups: uk.comp.os.linux,demon.tech.unix