It is the Zen vision W -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, December 03, 2007 12:00 PM To: [email protected] Subject: Nessus Digest, Vol 50, Issue 2 Send Nessus mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://mail.nessus.org/mailman/listinfo/nessus or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Nessus digest..." Today's Topics: 1. Re: nessus not finding tcp port 443 even though this is definitely active (IMAP Oskar) 2. Re: nessus not finding tcp port 443 even though this is definitely active (George A. Theall) ---------------------------------------------------------------------- Message: 1 Date: Mon, 03 Dec 2007 11:51:44 +0100 From: IMAP Oskar <[EMAIL PROTECTED]> Subject: Re: nessus not finding tcp port 443 even though this is definitely active To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed George, In regards to the double plugin entry: > end(PLUGIN_SET) > > begin(PLUGINS_PREFS) That was a poor cut and paste from me, there is just the one section. In regards to the nessus version, I don't understand that either. I did install 3.0.1 initially but upgraded that to the 3.0.6 version and the this Nessusclient version because it can export nessusrc format. Maybe these entries are a result of not removing the 3.0.1 version before installing the 3.0.6 version, or maybe some version strings have not been updated in nessus, or maybe it is as simple as restarting nessus, I really don't know ? [EMAIL PROTECTED]:~/nessus$ grep nessus nessusrc-20071130-05 # This file was automagically created by nessus nessusd_user = tst nessusd_host = 127.0.0.1 server_info_nessusd_version = 3.0.1 server_info_libnessus_version = 3.0.1 server_info_nessusd_version = 3.0.6 server_info_libnessus_version = 3.0.6 Nmap (NASL wrapper)[radio]:Timing policy : = Auto (nessus specific!);Normal;Insane;Aggressive;Polite;Sneaky;Paranoid;Custom Login configurations[password]:FTP password (sent in clear) : = [EMAIL PROTECTED] [EMAIL PROTECTED]:~/nessus$ apt-show-versions | grep nessus nessusclient 3.0.0.beta5 newer than version in archive nessus 3.0.6 newer than version in archive [EMAIL PROTECTED]:~/nessus$ /opt/nessus/sbin/nessusd -v nessusd (Nessus) 3.0.6. [build 283] for Linux (C) 1998 - 2007 Tenable Network Security, Inc. In regards to the ssl settings I have for "Test SSL based services : Known SSL ports". So that should be fine. As I recall Nessus always reports open ports, regardless of whether nessus has something to tell about that port or actually finds something on that port or not. Or has this behaviour changed and does Nessus not report on an open port if there is no finding against it ? Oskar George A. Theall wrote: > On 11/30/07 14:45, IMAP Oskar wrote: > > >> Nessus is not finding port 443 on a device on which I know it is open, >> > ... > >> Anybody any ideas to the why ? >> > ... > >> Ping the remote host[entry]:TCP ping destination port(s) : = built-in >> Ping the remote host[entry]:TCP ping destination port(s) : = extended >> Ping the remote host[entry]:TCP ping destination port(s) : = >> "21;22;23;25;53;69;79;80;110;111;113;123;135;137;138;139;143;161;256;259;264 ;265;389;443;445;497;500;515;548;900;953;981;993;1025;1028;1029;1080;1201;12 41;1433;1454;1723;1900;1917;2809;2869;2998;3128;3389;4100;5000;5600;8000;808 0;9001;9100;9495;18182;65553" >> > > These are only used by ping_host.nasl to determine whether a target is > up, not necessarily detect a service. > > >> # This file was automagically created by nessus >> nessusd_user = tst >> nessusd_host = 127.0.0.1 >> begin(PLUGIN_PREFS) >> > ... > > end(PLUGIN_PREFS) > > > > begin(PLUGIN_SET) > > ...................removed (all yes except for the DOS ones) > > > > end(PLUGIN_SET) > > > > begin(PLUGINS_PREFS) > > You have two PLUGINS_PREFS blocks instead of just one. Merge them and > pay particular attention to your choice of the "Services[radio]:Test SSL > based services" option. > > >> server_info_nessusd_version = 3.0.1 >> > > This is a bit old. > > George > ------------------------------ Message: 2 Date: Mon, 03 Dec 2007 10:43:46 -0500 From: "George A. Theall" <[EMAIL PROTECTED]> Subject: Re: nessus not finding tcp port 443 even though this is definitely active To: [email protected] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 12/03/07 05:51, IMAP Oskar wrote: > That was a poor cut and paste from me, there is just the one section. Would you mind sending me a copy of the config file as well as a KB for a target, both sanitized of any sensitive info? > As I recall Nessus always reports open ports, regardless of whether > nessus has something to tell about that port or actually finds something > on that port or not. Or has this behaviour changed and does Nessus not > report on an open port if there is no finding against it ? Nessus should report open ports as long as they fall in the specified port range. George -- [EMAIL PROTECTED] ------------------------------ _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus End of Nessus Digest, Vol 50, Issue 2 ************************************* _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
