Re: OpenSSL Applink - Mailing list pgsql-patches

From Tom Lane
Subject Re: OpenSSL Applink
Date
Msg-id 3260.1191077106@sss.pgh.pa.us
Whole thread Raw
In response to Re: OpenSSL Applink  ("Dave Page" <dpage@postgresql.org>)
Responses Re: OpenSSL Applink
List pgsql-patches
"Dave Page" <dpage@postgresql.org> writes:
>> From: Tom Lane <tgl@sss.pgh.pa.us>
>> ... It's not entirely clear whether BIO_new_fp() would avoid the
>> problematic calls, but it doesn't look like it'd be hard to try.

> The last version of the patch I posted uses BIO_new_file() in all cases, and (from memory) BIO_get_fp() in the
non-win32case to get a FILE* to pass to fstat. 

Did you manage to get rid of the bogus-error-message problem that
afflicted the first version of the patch?  If so, this way is fine.
If not, keeping control of file-opening in our own hands might be
a way to dodge that.

            regards, tom lane

pgsql-patches by date:

Previous
From: Simon Riggs
Date:
Subject: set_ps_display during recovery
Next
From: Zdenek Kotala
Date:
Subject: Re: pgcrypto: fix for broken solaris openssl, v03