If someone wants to create a separate web page to track fixes related to CVE number, that is fine. My guess is that most people reading the release notes don't care about the CVE numbers themselves (just that each release has all known security bugs fixed), and most bugs that are fixed don't have CVE numbers at commit time.
--------------------------------------------------------------------------- Peter Eisentraut wrote: > Bruce Momjian wrote: > > I am not excited about referencing error numbers from someone else. > > We know our errors better than anyone else, so I don't see the point. > > The point is, *we* might know our error numbers, but the rest of the > world doesn't. > > And CVE isn't just "someone". A large number of security groups, > government agencies, and OS distributors are involved there. Using CVE > numbers, the public can, say, correlate bugtraq or CERT announcements > or Red Hat or Debian bugs to PostgreSQL patches and releases. > Copy-and-pasting the CVE number into the patch message or release note > entry really isn't that much to ask for that service. > > -- > Peter Eisentraut > http://developer.postgresql.org/~petere/ > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
