Michael Schmitt wrote:
> Renaud Deraison wrote:
>
>> I'm not too keen on that for various reasons (the "family"
>> classification makes no sense anyway, I'd prefer to use keywords in the
>> future, to users will be able to view things the way the prefer).
>>
> That's a very good idea. Let's get rid of the families at all! In the
> frontend, the user may be able to define his own kind of "families"
> based on keywords. But we must define a reasonable set of keywords that
> are used in a uniform manner.
>
> Michael
>
Ugh....and ugh again! For reasons of "human tendencies", don't
go there. People tend to be lazy, uninformed and sloppy (all of
us), until we learn the hard way it pays to be otherwise. At
least with a basic categorization, you get at least ONE decent
grouping of scripts.
If you remove the family, and use keywords, how long do you
think it will be before there are many scripts that have absolutely
NO appropriate keywords in them at all? And, a keyword in
English doesn't necessarily match a keyword in another language.
So now results in a search in one language may not match the results
in another language due to a simplistic error in translation??
(E.g. was it keywords "CGI Abuse" or "CGI Abuses" to find that
script I wanted...)
You absolutely should have at least ONE set of groupings.
And, btw, using keywords to view things the way you want to right
now does not preclude getting rid of families - just enable
a keyword search - it's fast and easy to do, and won't even
require a server change - something that can be completely done
in the client.
Thomas
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.
