Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, Justin Clift <justin(at)postgresql(dot)org>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Vince Vielhaber <vev(at)michvhf(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Date: 2002-08-20 16:28:27
Message-ID: 200208201228.27251.lamar.owen@wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday 20 August 2002 12:15 pm, Tom Lane wrote:
> Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> > Umm, but what about the reply buffer overrun advisory? I've read this
> > whole thread, and the reply advisory (AFAICT, unless I've just hit delete
> > too quickly) has NOT been addressed.

> Yes it has. CVS logs show

> I'd put more stock in the concern level of the people making complaints
> if anyone had bothered to do even that much legwork. Without an offered
> patch against 7.2 branch, I don't think the folks who push out releases
> (which is not me, but Marc, Bruce, you, Trond, etc) should bother to
> take notice of the complaints at all.

If a patch is proffered to 7.2.1 to fix this, I'll be happy to roll a new
RPMset. I tend to agree with you on this detail, Tom.

I had just apparently missed that portion; thanks for the reminder.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian Weimer 2002-08-20 16:31:28 Re: [SECURITY] DoS attack on backend possible
Previous Message Tom Lane 2002-08-20 16:15:38 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in