nessus doesn't publish a 'banner' (telnet to that port and see) nessus services* nes and nasl's are smart enough to understand nessus.
if you have two interfaces, start in on only one of them (internal facing), -a option compile with tcp wrappers and use a 'twist echo '220 ESMTP Ready' or something fun for 'unfriendly' ip addresses. could firewall (or for more fun, 'divert' or proxy the port) don' t recommend firewall on nessus scanner, it interferes with the nessus scans sometimes. -- Michael Scheidell, CTO 561-999-5000, ext 1131 SECNAP Network Security Corporation Keep up to date with latest information on IT security: Real time security alerts: http://www.secnap.com/news _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
