Re: pgcrypto seeding problem when ssl=on - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: pgcrypto seeding problem when ssl=on
Date
Msg-id CACMqXC+ioKc7o96=mHb8+jBK1iqoupGz14H2D3rkKcOXfrUmkQ@mail.gmail.com
Whole thread Raw
In response to Re: pgcrypto seeding problem when ssl=on  (Noah Misch <noah@leadboat.com>)
Responses Re: pgcrypto seeding problem when ssl=on
List pgsql-hackers
On Fri, Dec 21, 2012 at 10:27 PM, Noah Misch <noah@leadboat.com> wrote:
> How about instead calling RAND_cleanup() after each backend fork?

Attached is a patch that adds RAND_cleanup() to fork_process().
That way all forked processes start with fresh state.  This should
make sure the problem does not happen in any processes
forked by postmaster.

Please backpatch.

...

Alternative is to put RAND_cleanup() to BackendInitialize() so only
new backends start with fresh state.

Another alternative is to put RAND_cleanup() after SSL_accept(),
that way core code sees no change, but other OpenSSL users
in backend operate securely.

--
marko

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: count(*) of zero rows returns 1
Next
From: Tom Lane
Date:
Subject: Re: pgcrypto seeding problem when ssl=on