Re: Reporting a security hole

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: ken(at)coverity(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Reporting a security hole
Date: 2004-04-21 01:55:02
Message-ID: 200404210155.i3L1t2U27566@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


You can send it to core(at)postgresql(dot)org, but I already saw your report on
the hackers list.

---------------------------------------------------------------------------

ken(at)coverity(dot)com wrote:
> I work at Coverity where we make a static analysis tool to find bugs in
> software at compile time. I think I found a security hole in
> postgresql-7.4.1, but I don't want to just report it to a public list. I
> sent email to security(at)postgresql(dot)org, hoping that the address existed,
> but I got no response.
>
> So where can I report a potential security hole?
>
> thanks,
> Ken Ashcraft
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-04-21 01:58:44 Re: pg_autovacuum crashes when query fails for temp tables
Previous Message Bruce Momjian 2004-04-21 00:39:20 Re: [Pgreplication-general] converting the DBMirror as peer-to-peer