Re: libpq3 + ssl memory leak

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Neil Conway <neilc(at)samurai(dot)com>, Olaf Hartmann <hao(at)telemedsys(dot)de>, pgsql-bugs(at)postgresql(dot)org, Sean Chittenden <sean(at)chittenden(dot)org>
Subject: Re: libpq3 + ssl memory leak
Date: 2003-12-19 02:28:40
Message-ID: 200312190228.hBJ2Sed15802@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane wrote:
> Neil Conway <neilc(at)samurai(dot)com> writes:
> > Okay, I've attached a patch that fixes the problem for me. The problem
> > turned out to be pretty simple: the PostgreSQL code (both backend and
> > frontend SSL support) was calling SSL_get_peer_certificate() without
> > properly free'ing its return value.
>
> Applied to 7.4 and HEAD.

Good. I have given up getting an update from the original bug reporter.

--
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-bugs by date

  From Date Subject
Next Message Tom Lane 2003-12-19 03:41:56 Re: BUG #1015: Got a signal 11 while trying to create a temp table
Previous Message Greg Sabino Mullane 2003-12-19 01:14:38 Re: plpgsql For SQLQuery Loop Flags Error