Felix Wolfsteller escribió: > iiuuc you aks whether the target machines are forced to run ssh on port 22. > > Short answer: code looks as if this would not be a problem, but haven't > tested. > > SSH should not be forced to run on port 22. Ideally the/a portscanner > discovers ssh running on a different port and registers this port in the > knowledge base (something that can be used by nvts to communicate). > Other ssh- related nvts should then look up this port and use it. > > I have seen this in code at some places. Usually 22 is used only if no entry > in the knowledge base was found (kind of a 'fallback' or 'default'). > > Please just give it a try and confirm. > > -- felix > > On Monday 11 May 2009 19:30:57 David Corcuera wrote: > >> Hi list, >> >> I've a doubt that documentation couldn't solve. Is it possible to make >> LSC using SSH ports different from normal 22? >> >> Thanks in advance for the help. >> >> dav >> >> _______________________________________________ >> Openvas-discuss mailing list >> [email protected] >> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss >> > > > Tested OK. I was asking this because it seemed as though LSC was not working when target was listening on port 2222. It should have been any credentials trouble.
dav _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
