Re: Stats Collector Error 7.4beta1 and 7.4beta2

From: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Stats Collector Error 7.4beta1 and 7.4beta2
Date: 2003-09-10 11:27:02
Message-ID: 3601.24.211.141.25.1063193222.squirrel@www.dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane said:
> Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
>> So either we do the random signature thing, which I would favor as a
>> one time be all, end all solution - or you do the actual from-address
>> based implementation by restoring the old IPV4 behaviour and adding
>> correct IPV6 behaviour.
>
> My feeling at this point is that it's not worth spending any effort on.
> But if someone wants to expend effort, let's go with Jan's
> random-signature idea. That is simple, unquestionably portable, and
> AFAICS it defends against more than the source-address check would
> defend against, even after we got it right. (Consider spoofed packet
> source addresses.)
>

I see that currently the check has been removed rather than fixed.

If someone can spoof the packet address isn't there also a possibility
that they can read your packets and see your random signature?

I'm not clear what would be gained by an attacker being able to insert
such spoofed packets into the stream, though. IOW, how big is the security
threat?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Koizar 2003-09-10 13:11:27 Re: Is it a memory leak in PostgreSQL 7.4beta?
Previous Message Andrew Dunstan 2003-09-10 11:09:18 Re: TCP/IP with 7.4 beta2 broken?