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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-bugs by date

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