On Thu, Jul 22, 2004 at 08:43:08PM +0200, Pavel Kankovsky wrote:
> On Thu, 22 Jul 2004, Renaud Deraison wrote:
>
> > It's not true any more - the fact is that these scripts will need to be
> > updated over time as well. Having a separate directory means more
> > maintenance headaches both from my point of view and the one of the
> > users.
>
> What about users who want to behave in a more intelligent way than
> click'n'drool? Rather than doing cursory checks of new ordinary plugins
> and much less frequent thorough checks of new trusted plugins, they'll
> have to do thorough checks of all new plugins. Wonderful.
That's wrong. First, from a security point of view, a plugin which
calls pread() is not more or less insecure than a plugin which can
call ssh_cmd_exec() - they both execute arbitrary commands, and
therefore you want to audit them both.
What I have in mind is the following :
- In Nessus 2.1.2 (hopefully) the tar archive will be signed
- Within the tar archive, only the sensitive plugins will be signed.
This means that you can very easily check a sensitive plugin just by
doing a :
grep -l '^#TRUSTED' *.nasl
in your plugin directory, and that will be it. Since you are a skilled
user, you can very easily modify nessus-update-plugins to NOT copy the
new 'trusted' plugins over into $prefix/lib/nessus/plugins/ and put them
in another directory for you to review first - it's far from difficult.
At the same time, it allows us to publish new plugins, bugfixes and
improvements in a very flexible way which does not force the user
to re-install the whole nessus-plugins archive.
-- Renaud
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
