Skip site navigation (1) Skip section navigation (2)

Re: Porting issue with openssl and no /dev/random

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruno Wolff III <bruno(at)cerberus(dot)csd(dot)uwm(dot)edu>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Porting issue with openssl and no /dev/random
Date: 2001-10-29 21:14:20
Message-ID: 14369.1004390060@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Bruno Wolff III <bruno(at)cerberus(dot)csd(dot)uwm(dot)edu> writes:
> I installed the client part of postgres on a Compaq Alpha running tru64
> Unix 4 (or what they are calling it these days) using the openssl library.
> This machine does not have random device and openssl's library insists
> on some random data in order to start up. This prevented me from running
> the software as downloaded. I made some changes to fe-connect.c to
> read ~/.rnd for initial state so I could use the feature.

> This isn't exactly a postgres problem, but it may be that you can check
> for this case (no /dev/random and openssl) and call the ssl functions
> to get random state from a file.

I believe we discussed this awhile back and decided that it wasn't a
good idea for Postgres to hack around what is really an OpenSSL bug.
IIRC, the problem was supposed to be fixed in an upcoming OpenSSL
release; do you have the latest openssl?

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tatsuo IshiiDate: 2001-10-30 01:02:09
Subject: Re: postgresql-7.1.3 bugs
Previous:From: Tom LaneDate: 2001-10-29 18:49:50
Subject: Re: Problems when inserting a very large sequence of records

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group