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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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've just installed Ubuntu 6.06, and I'd like to run x11vnc on it.
I've installed x11vnc, and it appears to run correctly, but I can't connect to it from my Windows box. I've since discovered that Ubuntu installs with all ports closed. How would a newbie open port 5900?
by default, ubuntu doesn't firewall anything (the policies for the chains are all set to ACCEPT)... having no firewall doesn't mean ports are "open"... the ports will be "closed" until something actually listens on a port... once you have something listening on a port, *then* the port is said to be "open"...
so basically, if you haven't changed ubuntu's default iptables firewall settings, then your issue is somewhere else - not with the host's firewall... maybe use netstat to make sure your program is actually listening on the port you expect it to...
I just want port 22 open for ssh, but I can't find out how.
There is no firewall installed by default - so do I need to install one? Can I open it without installing a firewall?
assuming you are referring to a stand-alone box: on ubuntu, even though it includes the iptables/netfilter firewall, no ports are filtered by default - so you simply need to make your ssh daemon listen on port 22 (or any other) and the port will automatically be opened...
My problem was using ssh to access my box. I thought the problem was the port was not open (which it wasn't), but the real problem was that Ubuntu installs only the ssh client (to ssh into other boxes) but not the ssh-server. This is an easy fix:
sudo apt-get install openssh-server
Now ssh server is installed, I can ssh into my box, the port is open, and all is well.
Make sure to read the ubuntuguide.org and secure your ssh-server so root login is disabled, etc.
the two daemons you listed are listening on the loopback interface (127.0.0.1), hence they won't be visible from another box... if you need them to listen on your WAN/LAN interface you'll need to adjust their config files accordingly and then restart them... your firewall's policies are all set to ACCEPT, and your only INPUT rule is also an ACCEPT, so it's not a firewall issue as you aren't doing any packet filtering...