Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd) - Mailing list pgsql-hackers

From Neil Conway
Subject Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd)
Date
Msg-id 87d6sdb6rw.fsf@mailbox.samurai.com
Whole thread Raw
In response to @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd)  (Vince Vielhaber <vev@michvhf.com>)
Responses Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in  (Vince Vielhaber <vev@michvhf.com>)
Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd)  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in  ("Marc G. Fournier" <scrappy@hub.org>)
List pgsql-hackers
Vince Vielhaber <vev@michvhf.com> writes:
> Here's yet another.

Should someone from the core team perhaps get in contact with this guy
and ask if he could get in contact with the development team before
publicizing any further security holes? AFAIK that is standard
operating procedure in most cases...

Second, it might be worth pushing a 7.2.2 release containing the fix
for this bug, as well as the datetime problem. If that sounds
reasonable to the people who have to do the most work on a new release
(e.g. Marc), I can volunteer to backport a fix for the datetime
problem.

Cheers,

Neil

-- 
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Proposal: make "opaque" obsolete
Next
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in