From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-www(at)postgresql(dot)org |
Subject: | Re: How to coordinate web team for security releases? |
Date: | 2007-02-05 20:12:28 |
Message-ID: | 17831.1170706348@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> So to keep it really under the hood would probably be quite difficult to do.
Certainly. We're not looking for something absolutely bulletproof, we
just don't want to read about it on pgsql-announce before the actual
release ;-). Postgres isn't the sort of target that is likely to have
blackhats tracking our anoncvs watching for interesting commits. We
think it's probably enough if we can keep the topic out of the public
mailing lists until the release announcement. Or at least, let's try
to accomplish that before worrying about anything tighter.
(Speaking of which, somebody can go ahead and approve those Security:
pgsql-commit messages now ...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2007-02-05 20:21:23 | Re: How to coordinate web team for security releases? |
Previous Message | Dave Page | 2007-02-05 20:11:58 | Re: How to coordinate web team for security releases? |