Re: Transparent column encryption

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Transparent column encryption
Date: 2022-10-13 13:43:21
Message-ID: 458eb162-c4a1-a55c-2f45-a7276366bbff@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06.10.22 17:19, Andres Freund wrote:
>>> psql error: stderr: 'OPENSSL_Uplink(00007FFC165CBD50,08): no OPENSSL_Applink'
>> What in the world is that about? What scant information I could find
>> suggests that it has something to do with building a "release" build against
>> an "debug" build of the openssl library, or vice versa. But this patch
>> doesn't introduce any use of openssl that we haven't seen before.
> It looks to me that one needs to compile, in some form, openssl/applink.c and
> link it to the application. No idea why that'd be required now and not
> earlier.

I have figured this out. The problem is that on Windows you can't
reliably pass stdio FILE * handles between the application and OpenSSL.
To give the helpful places I found some Google juice, I'll mention them
here:

- https://github.com/edenhill/librdkafka/pull/3602
- https://github.com/edenhill/librdkafka/issues/3554
- https://www.mail-archive.com/openssl-users(at)openssl(dot)org/msg91029.html

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Woodward 2022-10-13 13:58:42 Re: Transparent column encryption
Previous Message Dave Page 2022-10-13 13:38:06 Re: Tracking last scan time