Mailing List Archive

Idea: plugin file names are id.nasl
Hi,

Just thought that it would make my life easier if plugins were named as
id.nasl (or .nes). The current setup is that plugins essentially have
three separate primary keys - ID, name and filename. There's no point in
the filename primary key - it's a pain to choose a unique file name, and
it's a pain to find the filename based on ID. Really, the name shouldn't
be treated as a primary key (nessusd does this internally), but that's a
side issue as the name definitily should be unique.

Thoughts?

Paul

--
Paul Johnston
Security Specialist
Westpoint Limited
Albion Wharf, 19 Albion Street,
Manchester, M1 5LN
England
Tel: +44 (0)161 237 1028
Fax: +44 (0)161 237 1031
email: paul@westpoint.ltd.uk
web: www.westpoint.ltd.uk
Re: Idea: plugin file names are id.nasl [ In reply to ]
On Thursday 09 January 2003 04:52, Paul Johnston wrote:
> and it's a pain to find the filename based on ID. Really, the name
> shouldn't be treated as a primary key (nessusd does this internally),
> but that's a side issue as the name definitily should be unique.

$ grep script_id\(12345 *.nasl

It would be a pain to find a plugin whose name was just its its ID too.
When dealing with a huge directory of 1000+ plugins, I like being able to
get an idea what each one does just by glancing at it's name. Its easy to
see which plugins do SMB checks, which ones test a given application,
etc..

-HD
Re: Idea: plugin file names are id.nasl [ In reply to ]
On Thu, 9 Jan 2003, H D Moore wrote:

> $ grep script_id\(12345 *.nasl

Been there, done that, found it quite annoying when the number of
plugins I needed to examine exceeded 20 or so in a day.
Moreover, it does not work on non-NASL plugins.

> It would be a pain to find a plugin whose name was just its its ID too.

What about 12345_plugin_xyz.nasl (or ...nes etc.)?

--Pavel Kankovsky aka Peak [ Boycott Microsoft--http://www.vcnet.com/bms ]
"Resistance is futile. Open your source code and prepare for assimilation."