| Lists: | pgsql-hackers |
|---|
| From: | "Dann Corbit" <DCorbit(at)connx(dot)com> |
|---|---|
| To: | "Lamar Owen" <lamar(dot)owen(at)wgcr(dot)org>, "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 18:51:43 |
| Message-ID: | D90A5A6C612A39408103E6ECDD77B82906F4B4@voyager.corporate.connx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Lamar Owen [mailto:lamar(dot)owen(at)wgcr(dot)org]
> Sent: Monday, August 26, 2002 11:41 AM
> To: Dann Corbit; Bruce Momjian; Tom Lane
> Cc: Sir Mordred The Traitor; pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] @(#)Mordred Labs advisory 0x0007:
> Remove DoS in PostgreSQL
[snip]
> And, yes, I agree he IS providing a valuable service -- with
> that I have no
> complaints. But there is a distinct civility and culture to
> this list, and
> I'd like to see it stay that way.
I want to make it clear that I think the best way to report a problem is
with formal, rigorous, complete structure. That structure should be
known to the receiving body. If there is a procedure or standard form
for producing the needed information, it is better to follow the
standard procedure.
On the other hand (and the point I had hoped to make) some people like
to take lined paper and write on it sideways [Bradbury's "Fahrenheight
451" quote]. Instead of complaining that they are writing sideways on
the page, extract the information of value. If the can be convinced to
"stop writing in a perpendicular manner" so that the majority will be
more comfortable with it, so much the better. But standardized or not,
it can still contain information of great value.
| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | "Dann Corbit" <DCorbit(at)connx(dot)com>, "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 19:01:23 |
| Message-ID: | 200208261501.23009.lamar.owen@wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-hackers |
On Monday 26 August 2002 02:51 pm, Dann Corbit wrote:
> I want to make it clear that I think the best way to report a problem is
> with formal, rigorous, complete structure. That structure should be
> known to the receiving body. If there is a procedure or standard form
> for producing the needed information, it is better to follow the
> standard procedure.
Ok, let's do that then. SOP is to use the bug reporting form contained on the
website, which posts a bug report to pgsql-bugs(at)postgresql(dot)org, which is the
canonical bugreport list. That is if we want to get that formal.
> But standardized or not,
> it can still contain information of great value.
Yes, it can. I can use steganography to issue an RPM release announcement,
too. But will it be effective? :-)
If it isn't read, it won't be acted upon. His announcements have been a
difficult read, that's all. The substance is OK; the presentation is lacking,
IMHO.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11