Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
11-10-2003, 10:06 PM
|
#1
|
Member
Registered: Aug 2003
Location: Rochester, MN, U.S.A
Distribution: Gentoo
Posts: 987
Rep:
|
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
|
|
|
11-10-2003, 10:21 PM
|
#2
|
Senior Member
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113
Rep: 
|
I commented out my entire inetd.conf. Can't remember what else. Whichever one a cracker gets through is the most dangerous.
|
|
|
11-10-2003, 10:40 PM
|
#3
|
Member
Registered: Aug 2003
Location: Rochester, MN, U.S.A
Distribution: Gentoo
Posts: 987
Original Poster
Rep:
|
thanks that worked.
could someone explain why this works, or just point me in the right direction
|
|
|
11-10-2003, 10:57 PM
|
#4
|
Member
Registered: Nov 2003
Location: Ithaca, NY
Distribution: Mac OS X, FreeBSD, Slackware
Posts: 52
Rep:
|
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.
|
|
|
11-10-2003, 11:33 PM
|
#5
|
Senior Member
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113
Rep: 
|
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.
|
|
|
11-10-2003, 11:40 PM
|
#6
|
Member
Registered: Aug 2003
Location: Rochester, MN, U.S.A
Distribution: Gentoo
Posts: 987
Original Poster
Rep:
|
" 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
|
|
|
11-11-2003, 12:08 AM
|
#7
|
Senior Member
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113
Rep: 
|
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. 
|
|
|
11-11-2003, 12:33 PM
|
#8
|
Member
Registered: Nov 2003
Location: Ithaca, NY
Distribution: Mac OS X, FreeBSD, Slackware
Posts: 52
Rep:
|
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.
|
|
|
11-11-2003, 12:39 PM
|
#9
|
LQ Guru
Registered: Jan 2001
Posts: 24,149
|
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.
|
|
|
11-11-2003, 05:26 PM
|
#10
|
Senior Member
Registered: Feb 2003
Distribution: Slackware
Posts: 4,113
Rep: 
|
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.
|
|
|
11-11-2003, 10:05 PM
|
#11
|
LQ Newbie
Registered: Jul 2003
Location: State of confusion (Wisconsin)
Distribution: Slackware 10.2 and Current
Posts: 29
Rep:
|
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.
|
|
|
03-24-2006, 12:21 PM
|
#12
|
LQ Newbie
Registered: Aug 2004
Posts: 19
Rep:
|
I have the same problem. Anyone have the solution?
|
|
|
03-24-2006, 01:09 PM
|
#13
|
Member
Registered: Aug 2004
Location: Aguascalientes, AGS. Mexico.
Distribution: Slackware 13.0 kernel 2.6.29.6
Posts: 816
Rep:
|
what's the 113/auth port for?
|
|
|
03-24-2006, 01:28 PM
|
#14
|
LQ Newbie
Registered: Aug 2004
Posts: 19
Rep:
|
I think I need it to authorize my machine to the WLAN of my college.
|
|
|
03-24-2006, 05:15 PM
|
#15
|
LQ Newbie
Registered: May 2005
Location: Vilnius Lithuania
Distribution: Slackware 10.1
Posts: 4
Rep:
|
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.
|
|
|
All times are GMT -5. The time now is 03:52 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|