From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | w^3 <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Purge obsolete security updates? |
Date: | 2011-02-01 00:08:30 |
Message-ID: | 11141.1296518910@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> ... currently has security patch information going back to 2004. I'd
> like to cut everything which only applies through version 8.0 as
> obsolete. This would mean cutting all notices starting with
> CVE-2006-0678.
> Further, I'd like to make a general policy that we cut security
> information from this page a year after the last referenced version goes
> EOL (e.g. we'd delete CVE-2006-5542 this November).
-1 on both. The fact that we're not releasing new updates for old
versions is miles away from suppressing information about them.
Furthermore, having those notices up there might help to spur people to
update off those versions, which is what we really want. If we remove
all the old notices it is likely to leave the impression "hey, 7.4 is
much more bug-free than the newer versions, so I should stay on it".
If anything, I'd like to see us *add* the older versions to the newer
notices when relevant. We want people to realize that these holes exist
and are unfixed in old branches, not think they're secure.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2011-02-01 06:37:28 | Re: Purge obsolete security updates? |
Previous Message | Josh Berkus | 2011-01-31 23:52:03 | Re: Purge obsolete security updates? |