LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-10-2003, 10:06 PM   #1
shanenin
Member
 
Registered: Aug 2003
Location: Rochester, MN, U.S.A
Distribution: Gentoo
Posts: 987

Rep: Reputation: 30
which one is the biggest risk?


I have these ports shown when I run nmap

21/tcp open ftp
37/tcp open time
79/tcp open finger
113/tcp open auth
6000/tcp open X11

Which one is the biggest swcurity risk, and how would I shut down the service. I am using slackware 9.1I have these ports shown when I run nmap
 
Old 11-10-2003, 10:21 PM   #2
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
I commented out my entire inetd.conf. Can't remember what else. Whichever one a cracker gets through is the most dangerous.
 
Old 11-10-2003, 10:40 PM   #3
shanenin
Member
 
Registered: Aug 2003
Location: Rochester, MN, U.S.A
Distribution: Gentoo
Posts: 987

Original Poster
Rep: Reputation: 30
thanks that worked.

could someone explain why this works, or just point me in the right direction
 
Old 11-10-2003, 10:57 PM   #4
h3pc4t
Member
 
Registered: Nov 2003
Location: Ithaca, NY
Distribution: Mac OS X, FreeBSD, Slackware
Posts: 52

Rep: Reputation: 15
inetd is the Internet "super-server" daemon, which listens on a number of ports, and only starts up the requested service when needed. To disable:

. /etc/rc.d/rc.inetd stop
chmod -x /etc/rc.d/rc.inetd

/etc/inetd.conf has all of the settings for inetd - read man inetd.

You should consider what you need inetd for. By default, inetd runs four services: ftp, finger, auth, and time. FTP is useful, the others usually aren't (and finger is a security risk in some ways). If you need FTP, you're better off using SFTP, which is handled by sshd.

Just as a general rule - if you don't need it, don't run it.

Also, regarding the X11 port - it is used for X11 forwarding, which I find very useful. If you need more info on this, feel free to ask.
 
Old 11-10-2003, 11:33 PM   #5
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
Okay, I'll ask. I think that's the only thing I have open and I left it just because I couldn't figure out if I needed it or not. (The X11, I mean.) I assume it only has to do with accessing (or being) a remote X server rather than on my own box, but wasn't sure. Also, is my understanding correct that I only need ftp if I'm serving ftp? I have it shut and still access ftp sites.
 
Old 11-10-2003, 11:40 PM   #6
shanenin
Member
 
Registered: Aug 2003
Location: Rochester, MN, U.S.A
Distribution: Gentoo
Posts: 987

Original Poster
Rep: Reputation: 30
" is my understanding correct that I only need ftp if I'm serving ftp? I have it shut and still access ftp sites."

that is my understanding
 
Old 11-11-2003, 12:08 AM   #7
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
Cool. Just wanted to make sure I didn't get bit by anything. Probably the same thing goes for X11 - the whole bundle is useless for a lonely ol' workstation/www client.
 
Old 11-11-2003, 12:33 PM   #8
h3pc4t
Member
 
Registered: Nov 2003
Location: Ithaca, NY
Distribution: Mac OS X, FreeBSD, Slackware
Posts: 52

Rep: Reputation: 15
Yes, the ftp provided by inetd (proftpd 1.2.9) is only needed if you want to run an FTP server. And as I said, you should be using SSH, which allows you to access your files securely using SFTP. Normal FTP is unencrypted!

I'm not sure how to stop X11 from listening on port 6000 - however, without a specific setting in /etc/ssh/sshd_config (and sshd running), it is *not* accessible remotely. If you would like to connect to your X server remotely, use the following instructions.

In /etc/ssh/sshd_config on your machine, uncomment X11Forwarding, and change it to 'yes'. (Re)start sshd. Then, from another machine with its own X server, type:

ssh -X user@host

Once you're logged in, any X app you run will open on the local display.
 
Old 11-11-2003, 12:39 PM   #9
trickykid
LQ Guru
 
Registered: Jan 2001
Posts: 24,149

Rep: Reputation: 271Reputation: 271Reputation: 271
Quote:
Originally posted by shanenin
" is my understanding correct that I only need ftp if I'm serving ftp? I have it shut and still access ftp sites."

that is my understanding
Restart the inetd daemon for changes to take affect after editing, etc.

And you can do a startx -nolisten tcp so it doesn't broadcast on port 6000, etc.
 
Old 11-11-2003, 05:26 PM   #10
slakmagik
Senior Member
 
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113

Rep: Reputation: Disabled
Quote:
Originally posted by trickykid
Restart the inetd daemon for changes to take affect after editing, etc.

And you can do a startx -nolisten tcp so it doesn't broadcast on port 6000, etc.
Cool. As long as it's not needed, I'll do that.
 
Old 11-11-2003, 10:05 PM   #11
GrayGhost
LQ Newbie
 
Registered: Jul 2003
Location: State of confusion (Wisconsin)
Distribution: Slackware 10.2 and Current
Posts: 29

Rep: Reputation: 15
Anyone know how to stop X from listening on port 6000 when using KDM? I put -nolisten tcp in my /usr/X11R6/bin/startx script but no joy. Appreciate any help.
 
Old 03-24-2006, 12:21 PM   #12
skybell
LQ Newbie
 
Registered: Aug 2004
Posts: 19

Rep: Reputation: 0
I have the same problem. Anyone have the solution?
 
Old 03-24-2006, 01:09 PM   #13
raska
Member
 
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816

Rep: Reputation: 31
what's the 113/auth port for?
 
Old 03-24-2006, 01:28 PM   #14
skybell
LQ Newbie
 
Registered: Aug 2004
Posts: 19

Rep: Reputation: 0
I think I need it to authorize my machine to the WLAN of my college.
 
Old 03-24-2006, 05:15 PM   #15
Romas
LQ Newbie
 
Registered: May 2005
Location: Vilnius Lithuania
Distribution: Slackware 10.1
Posts: 4

Rep: Reputation: 0
Re

Quote:
Originally Posted by GrayGhost
Anyone know how to stop X from listening on port 6000 when using KDM? I put -nolisten tcp in my /usr/X11R6/bin/startx script but no joy. Appreciate any help.
Where did you put it?
It should look like this: serverargs="-nolisten tcp"

Works for me.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Biggest Newb Of All Time! n00bie777 Linux - Newbie 7 11-15-2004 07:27 AM
One of my biggest challenge! gcclinux JDS 1 10-23-2004 10:15 AM
Will a RISK Processor Run on Linux, PA-RISK 8500 at 400MHz CPU IBNETMAN79 Linux - General 2 03-08-2002 07:09 PM
Will a RISK Processor Run Linux, PA-RISK 8500 CPU IBNETMAN79 Linux - Newbie 1 03-08-2002 06:49 PM
Will A RISK CPU Run Linux, HP PA-RISK 8500 CPU IBNETMAN79 General 0 03-08-2002 06:39 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:52 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration