bugtraq - Re: local Calendar System v1.1 (lcStdLib.inc) Remote File Include

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1170108679.13609.17.camel@localhost>
Date: Mon, 29 Jan 2007 16:11:19 -0600
From: Simple Nomad <thegnome@...c.org>
To: Gadi Evron <ge@...uxbox.org>
Cc: Stefano Zanero <s.zanero@...urenetwork.it>, trzindan@...mail.fr,
	bugtraq@...urityfocus.com
Subject: Re: local Calendar System v1.1 (lcStdLib.inc) Remote File Include

On Mon, 2007-01-29 at 13:00 -0600, Gadi Evron wrote:
> How can we all automate the testing process for fake vulns in and list
> them as such without overburdening OSVDB, CVE, Milworm and SecuriTeam?

How about letting them get posted to bugtraq as ppl test them out
anyway? Usually the testing reports from various ppl on bugtraq bring up
extra info such as "works on the previous version too" or "if foo=0 is
in the config it doesn't work" etc, otherwise someone will want ALL
versions tested before posting.

Bugtraq is probably about as automated as it gets, unless someone wants
to send all their stuff to iDefense or TippingPoint who probably aren't
going to touch the latest lame xss bug or php app bug.

-SN