Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i am fairly new to linux and need to find out about the "X" windows listening on port 6000. i have spent some time trying to harden my system and was disappointed when i went to a web site to find out that my system is only 44% secure.
after running the netstat command as root, i found that my system was listening on port 6000 and i would like to know, from any guru's out there, how i can close, or stealth, this port....????
nothing too technical please....i am still in the very beginnings of learning.
Closing down the port with iptables is a pefectly legit solution (although your syntax isn't quite right). And the one-liner would be
iptables -A INPUT -p ALL -i eth0 --dport 6000 -j DROP
However, if you never plan on using X remotely, why not shut it down? This has two advantages, First, if something goes wrong with the firewall, there is still no way to get in this way because nothing is listening to port 6000. Second, whatever resources are being used by X to listen to 6000 are freed.