Re: @(#)Mordred Labs advisory 0x0007: Remove DoS in PostgreSQL

From: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Sir Mordred The Traitor <mordred(at)s-mail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: @(#)Mordred Labs advisory 0x0007: Remove DoS in PostgreSQL
Date: 2002-08-26 17:50:09
Message-ID: 200208261350.09058.lamar.owen@wgcr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Monday 26 August 2002 12:59 pm, Bruce Momjian wrote:
> Tom Lane wrote:
> > It may indeed make sense to put a range check here, but I'm getting
> > tired of hearing the words "dos attack" applied to conditions that
> > cannot be exploited to cause any real problem. All you are
> > accomplishing is to spread FUD among people who aren't sufficiently
> > familiar with the code to evaluate the seriousness of problems...

> It isn't fun to have our code nit-picked apart, and Sir-* is over-hyping
> the vulnerability, but it is a valid concern. The length should
> probably be clipped to a reasonable length and a comment put in the code
> describing why.

The pseudo-security-alert format used isn't terribly palatable here, IMHO. On
BugTraq it might fly -- but not here. A simple 'Hey guys, I found a possible
problem when.....' without the big-sounding fluff would sit better with me,
at least. The substance of the message is perhaps valuable -- but the
wrapper distracts from the substance.

And dealing with a real name would be nice, IMHO. Otherwise we may end up
with 'SMtT' as the nickname -- Hmmm, 'SMitTy' perhaps? :-) Reminds me of
'Uncle George' who did quite a bit for the Alpha port and then disappeared.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-08-26 18:14:58 Re: @(#)Mordred Labs advisory 0x0007: Remove DoS in PostgreSQL
Previous Message Bruce Momjian 2002-08-26 17:35:40 Re: Queries using rules show no rows modified?