Thanks Thomas. I'll continue testing... One other question though... To help me limit the loaded plugins used for the scans...
The client can send the list of plugins it would like to use. I'm assuming this is done with CLIENT <|> PREFERENCES <|> plugin_set <|> ... What is the syntax for the plugin_set pref? Is it a comma-delimited list of OIDs? Or do I send a separate plugin_set pref for every plugin such as: plugin_set <|> 12345 plugin_set <|> 12346 ... How would I set my plugin set from the client? Thanks again! Shawn Thomas Reinke wrote: > Shawn Duffy wrote: >> Hello all, >> >> As I've mentioned in previous emails recently, I'm writing an OpenVAS >> client in PHP. I've managed to connect to the OpenVAS server, log in, >> retrieve plugins, and start a scan. But, the scan inevitably hangs at >> some point... usually, the same point. >> >> So I wanted to know if someone could walk through what the expected >> OTP conversation would look like between the client and server. I've >> read through the OTP docs but I'm still having trouble. This is what >> the conversation looks like now: >> >> Client: < OTP/1.0 > >> Server: < OTP/1.0 > >> Client: Logs in >> Client: CLIENT <|> PREFERENCES <|> >> ... list of prefs ... >> I've been sending an empty prefs list to keep things simple >> <|> CLIENT >> Server sends its preferences >> Client: CLIENT <|> LONG_ATTACK >> length of targets >> targets (just one target in this case) >> >> After this is all done, the server starts sending status messages and >> info about the scan. But after about a hundred lines or so, it just >> stops doing anything. The logs on the OpenVAS server aren't saying >> that anything is wrong, the process list still shows that openvasd is >> still performing the scan but it's just hanging. So, I'm assuming I'm >> not using the protocol correctly. >> >> Can someone let me know what a basic conversation between the client >> and server looks like, in order, so I can try to troubleshoot? I'll >> have some follow-up questions as soon as I get a basic idea of what >> the conversation looks like, I'm sure. > > That looks more or less right. If it is hanging, it is usually becase > of a plugin that is taking a long time to execute. > A couple of things you could check: > > 1) Check the logs and see if you see the "launching NNNN.nasl" lines > and match them against the "NNNN.nasl ... finished" lines. > > 2) Do a simple "ps" and look for anything with "nasl" in the line. > It should show you which plugins are running, and will give you > a hint as to where it is getting stuck. > > Once you successfully launch a scan, providing you stay connected > to the server, there is no other interaction needed. The server > spews all the results out as they come in, and at the end sends > the one line > "SERVER <|> BYE <|> BYE <|> SERVER" > > to indicate things are done. > > Thomas > -- > SecuritySpace Support > > _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
