Re: Incomplete OpenPKG reference in apache_log_injection.nasl

Renaud Deraison <[email protected]>
Newsgroups gmane.comp.security.nessus.devel
Message-ID <[email protected]>
On Mon, Jul 05, 2004 at 04:53:15PM +0200, Jan Fredrik Leversund wrote:
> Maybe it shouldn't have been fixed afterall...
> 
> All SUSE references seem to suffer from a similar problem. The 
> Announcement IDs are formatted like this: SUSE-SA:YYYY:NNN where YYYY is 
> the yeah and NNN is the announcement number for that year. Trouble comes 
> when you want to reference it, and all their advisory pages are named 
> YYYY_NNN_package.html and sometimes the NNN is just NN, depending on 
> which year YYYY is. On top of that, anything pre-2002 is not to be found 
> anywhere on their site... It's all very unstructured.

Yes, SuSE is nothing but consistent in their security pages - that's
really a pain. 

> So what it comes down to is this: Should the nessus references try to 
> compensate for this kind of odd behaviour, or should the references be 
> as simple as possible? Afterall, it IS possible to find the information 
> based on the simple form, it just takes a bit of manual searching.

I don't think it's really our place to do that. As long as OSVDB,
Bugtraq and CVE references are working, I don't care much about the
others.
				-- Renaud
_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.