Hi,

> as you can see, this is only debug information, nothing *wrong* with
> this. Indeed, for the moment, we rely on timeout conditions to make sure
> that the whole message as been received before processing it.

It's strange. It creates the script file in /tmp/w3af-script... and the XML 
report in /tmp/w3af-report...
But in the gsa no report is generated.

> The second issue is, can I create a target using the slash? For example:
> I wanna scan a website "mywebsite/index", but it doesn't work, because the 
> gsa doesn't accept the slash (/).
> In this case, I get the error message "Error in host specification".

> This indeed looks more like an error. Do you think that you're
> proficient enough in python to try to find the root of the issue ? I'll
> be glad to integrate a patch from you !

Guess the target thing isn't a fault in the python code. Reckon the gsa accepts 
the backslash only for a netmask like 192.168.1.0/24. Creating a target like 
localhost/mywebsite for scanning a website results in an error. So the root of 
the issue is in the gsa, I think.
The w3af-python wrapper gets the taget from gsa and it doesn't matter if the 
target looks like "localhost/mywebsite". 

Only an assumption, maybe I'm wrong...

Thanks.




----------------------------------------------------------------
Profitieren Sie von der sicheren E-Mail-Übertragung Ihrer Daten mit einer 
kostenlosen E-Mail-Adresse der Telekom.
www.t-online.de/email-kostenlos


_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to