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

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Dann Corbit <DCorbit(at)connx(dot)com>
Cc: Neil Conway <neilc(at)samurai(dot)com>, Mark Pritchard <mark(at)tangent(dot)net(dot)au>, Justin Clift <justin(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Date: 2002-08-20 06:21:06
Message-ID: 3D61DFD2.55D0FA18@fourpalms.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> To simply decide not to fix it means:
<snip>
> What I am saying is that there is nothing that could possibly be more
> important than fixing this, except some other known problem that could
> also cause billions of dollars worth of damage. Are there any such
> problems besides the buffer overrun problems?

This is an open source project. If you, or others with similar strong
feelings about what is important to you, would like to submit patches in
those areas I'm sure that they would be looked on favorably.

To simply insist that everyone else have the same priorities on any
topic is a bit unrealistic. However, I'd hope that if there are folks
who look at this particular issue with your PoV they would speak up and
think about helping out. If you didn't state a strong opinion on the
topic then others might never catch on that there is a potential issue,
let alone that they could contribute to a solution...

- Thomas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Pritchard 2002-08-20 06:26:57 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Previous Message Mark Pritchard 2002-08-20 06:15:03 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in