You could use CVE, Postgre's security page doesn't seem to sync with their CVE entries, even though they reference CVE entries on their comprehensive security page.
http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=postgresql http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mysql JW On Sat, May 22, 2010 at 10:51 AM, Rob Wultsch <wult...@gmail.com> wrote: > On Sat, May 22, 2010 at 5:44 AM, Martin Gainty <mgai...@hotmail.com> > wrote: > > Good Morning Rob- > > > > one vulnerability (with UDFs) > > http://dev.mysql.com/tech-resources/articles/security_alert.html > > > > a manager considering a enterprise-wide security solution may want > > to consider Oracle Identity Manager (with Glassfish 3.2) > > > http://under-linux.org/en/content/oracle-introduces-schedule-for-glassfish-556/ > > > > Does this help? > > Martin Gainty > > Martin, > > Thank you for the reply. > > The guys across the street have a single page with cliff notes about > every vulnerability effecting every supported version*. The page I > noted was comprehensive. Martin, what you listed was a page with an > single vuln and a page which looks like a product. > > The grass is looking pretty darn green on the other side of the street. > > *And they support all the way back to 7.4, which is equivalent to 4.1 > era. 2005 is not that long ago. > -- > Rob Wultsch > wult...@gmail.com > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/mysql?unsub=joh...@pixelated.net > > -- ----------------------------- Johnny Withers 601.209.4985 joh...@pixelated.net
