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.
I recently scanned myself using nessus, and to my suprise firestarter crashed. I ran this scan a couple of more times to make sure it was definetly nessus and yip it was. It appears it only crashes the GUI, because when I scan myself [nmap] after the crash my ports are still filtered. Is it because I am using the dangerous plug-ins that it is crashing...????
I haven't heard of that before, what version of firestarter are you running? You might want to go through the list of "dangerous" plugins one-by-one and see if you can narrow down which one kills firestarter. You could probably submit a bug report to the firestarter team once you narrow it down.
Can someone else with firestarter reproduce this??
Thanks for replying, I am going to work my through the plug-ins (when I have time) and will post the results here. Chort the X11 tests were the ones which I thought might be causing it..... I have managed [in the past] to scan myself successfully on the same system using Nessus, and it returned a result that the the X11 port 6000 was open, although it was not accepting connections. To be a more explanatory, during the scan my firestarter GUI turns blank, in the same way some programs crash in Linux when the only way to kill the program is through, killall -9 <prog-name>
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.