I'm still working on getting os_fingerprint.nasl working (among other
things, as mentioned in a previous e-mail). Before, the plugin itself was
not found. I updated my plugins again today, and now it exists, but cannot
run because "'os_fingerprint.nasl' depends on 'rio_karma_detect.nasl' which
could not be found". I did a search for this on the Nessus website, and the
closest I could find was "Rio Karma Network Port", which according to the
description is available to Direct feed users only. So, I have a few
questions about this.
1. Will this be made available to Registered users withing 7 days? I ask
because the description does not say that it is "currently only available",
just only "available."
2. Is there any way to run os_fingerprint.nasl without the Rio Karma
support? Can I just comment that out of the dependency list, or something
similar? Franky, I don't care about detecting such devices on my network.
3. I don't mean to be inflammatory with this question, but I have to ask -
Is this kind of breakage going to become common with the separate feeds?
Whereas in the good old days with a single feed any updates and dependencies
were automatically resolved because everything was available, that's not
true anymore. From what I can understand, updating an existing plugin to
use a new plugin will cause the existing plugin to fail for seven days until
the new plugin becomes available - or forever, if using the GPL food. Has
any thought been given to this?
Thanks,
--
Jared
_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus
