[Openvas-discuss] Missleading messages about opened SSH-Port (22)

Geoff Galitz geoff at galitz.org
Fri Sep 11 14:05:06 CEST 2009



Hi there.

What portscanners are you using?  Are you sure your target selection is
correct?  Incorrect network values in the target selection can result in
some pretty behavior.

-geoff

---------------------------------
Geoff Galitz
Blankenheim NRW, Germany
http://www.galitz.org/
http://german-way.com/blog/


> -----Original Message-----
> From: openvas-discuss-bounces at wald.intevation.org [mailto:openvas-discuss-
> bounces at wald.intevation.org] On Behalf Of Ewgenij Zharovsky
> Sent: Freitag, 11. September 2009 12:38
> To: openvas-discuss at wald.intevation.org
> Subject: [Openvas-discuss] Missleading messages about opened SSH-Port (22)
> 
> Hello everybody,
> I'm new to this list. I did some security scans with OpenVAS for my
> employer and ran into the following problem:
> OpenVAS reports the SSH port (22) to be opened almost on every run. Even
> in a run over a range of IPs, it gives me an opened SSH port for ips where
> actually no machine is running. As well as for machines, where the 22nd
> port is blocked by the firewall... My question is, is this a bug or a
> feature and if there is a possibility to determine _reliably_ if the SSH
> port is opened or closed on a certain machine. And if it is possible, then
> what configuration shall I try for the OpenVAS?
> Thanks in advance,
> Evgeniy
> 
> 
> 
> 
> _______________________________________________
> Openvas-discuss mailing list
> Openvas-discuss at wald.intevation.org
> http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss




More information about the Openvas-discuss mailing list