That did the trick. Only problem is that find_service2.nasl already had code in there to detect an FTP server returning the 220 but needed the word FTP in the banner somewhere as well. It also said in the comments that some SMTP servers will respond with a 220. Not the most elegant solution but I already know that port is an FTP server anyway, so I can just inject the modified nasl script before I do a scan on that device.
Thank you for the quick response. Brian -----Original Message----- From: Michael Scheidell [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2003 16:19 To: Hildebrand, Brian Cc: Nessus (E-mail) Subject: Re: Oddball FTP Server > I have an oddball FTP server I am working with that runs without an initial banner > and on an oddball port. I want Nessus to throw the FTP checks at it, but Nessus does > not know what kind of service it is. It simply comes up to a logon like this: maybe edit the find_services2.nasl and force it to register as an ftp server? -- Michael Scheidell, CEO SECNAP Network Security, LLC Sales: 866-SECNAPNET / (1-866-732-6276) Main: 561-368-9561 / www.secnap.net Looking for a career in Internet security? http://www.secnap.net/employment/ ---------------------------------------- The information transmitted in this message is intended only for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this document.
