Re: Stats Collector Error 7.4beta1 and 7.4beta2

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, Kurt Roeckx <Q(at)ping(dot)be>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, akavan(at)cox(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stats Collector Error 7.4beta1 and 7.4beta2
Date: 2003-09-05 18:50:11
Message-ID: 3F58DAE3.5080400@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

> I was about to say "I give up, let's just take out the comparison".
> Your point is interesting but easily avoided; if we aren't going to check
> fromaddr anymore then there's no need to use recvfrom(), it could as
> well be recv() and save the kernel a few cycles.

Which then get's us back to your concern about assuming that HPUX and
Linux manpages can be taken as "every platform will" and hope all
kernels will limit the sender for recv() to the connected address.

Since all involved processes are children of the postmaster, we can add
some other, random number based security signature into the message
itself. Noone outside will know what that is, it's really hard to guess
and can be checked with a few int32 compares, not even a function call
required.

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-09-05 18:59:36 Re: Stats Collector Error 7.4beta1 and 7.4beta2
Previous Message Tom Lane 2003-09-05 18:48:06 Re: 64-bit pgsql