From: George A. Theall (thealltenablesecurity.com)
Date: Fri Dec 09 2005 - 12:58:05 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Fri, Dec 09, 2005 at 01:04:46PM -0500, Matt Van Mater wrote:

> I think you meant to write:
> print $1, " = ", $2, "\n\n";

I bet you didn't try it that way - it needs to be $3 to account for the
parens in $keypat.

> But that aside, this is very similar to what I was thinking about
> changing my script to but I think it would make your parsing routine a
> somewhat slower.

Short-term, the descriptions are unlikely to be cleaned up. So you're
faced with making mods to your parsing routine to handle the "messy"
data. Yes, that's going to be slower, but I suspect it's likely to be
one that at least works.

> I agree. I was trying to think of a writing a script to parse the
> nasl files and find the ones that have "non standard" output format.
> No matter how you look at it, I think they will be somewhat unpleasant
> to fix and may require hands on attention to fix.

Perhaps "improve" would be a better word than "fix"... After all, the
description's are not "broken", are they?

> I suppose you could
> make the script find the output irregularities and then actually
> automatically rewrite the nasl
> in the correct format, but that doesn't sound like a whole lot of fun
> to me and may not be feasible.

Given how non-standard the descriptions currently are, I don't think an
automated solution would be a good idea.

George
--
thealltenablesecurity.com
_______________________________________________
Nessus-devel mailing list
Nessus-devellist.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus-devel

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]