Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
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.
netstat -atn | grep "LISTEN" does not include the port in question (113), and iptables isn't running. When I scanned it with nmap 4.11 it was on the box itself (e.g. I did nmap 127.0.0.1). When I scanned it with nmap 3.93 it was from an external computer, but I made sure the open port was not from another computer on the network (no other computers on the ip at that time).
netstat -atn | grep "LISTEN" does not include the port in question (113), and iptables isn't running.
okay...
Quote:
When I scanned it with nmap 4.11 it was on the box itself (e.g. I did nmap 127.0.0.1).
well, i do find it kinda weird that this would give you a "filtered" result...
Code:
win32sux@candystore:~$ nmap -p 113 127.0.0.1
Starting Nmap 4.03 ( http://www.insecure.org/nmap/ ) at 2007-02-23 15:18 EST
Interesting ports on localhost (127.0.0.1):
PORT STATE SERVICE
113/tcp closed auth
Nmap finished: 1 IP address (1 host up) scanned in 0.112 seconds
Quote:
When I scanned it with nmap 3.93 it was from an external computer, but I made sure the open port was not from another computer on the network (no other computers on the ip at that time).
what open port?? you said it appeared as "closed" - which would make perfect sense if there's no iptables rules and nothing listening on port 113...
just curious: have you seen anything in the changelog which might explain why your 4.11 is showing 113 on localhost as "filtered"??
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.