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

Re: PRNG not seeded => Seg.Fault

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Pillinger <S(dot)M(dot)Pillinger(at)cs(dot)bham(dot)ac(dot)uk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: PRNG not seeded => Seg.Fault
Date: 2001-11-11 02:10:59
Message-ID: 17707.1005444659@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Stephen Pillinger <S(dot)M(dot)Pillinger(at)cs(dot)bham(dot)ac(dot)uk> writes:
>    Attempting to connect via an SSL aware psql client machine that doesn't
>    have a PRNG seed causes the backend to generate a Segmentation Fault.

Well, removing all hope of reporting SSL-generated errors doesn't seem
like a good solution ;-) ... but evidently we need to guard against SSL
returning a NULL instead of an error string.  Fix committed.  Thanks
for the report!

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2001-11-11 02:31:32
Subject: Bug #514: Backend crashes periodically
Previous:From: Tom LaneDate: 2001-11-10 18:39:19
Subject: Re: Bug #513: union all changes char(3) column definition

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