diff options
| author | Stephen Frost <sfrost@snowman.net> | 2013-08-01 01:15:45 -0400 |
|---|---|---|
| committer | Stephen Frost <sfrost@snowman.net> | 2013-08-01 01:24:01 -0400 |
| commit | 0b821b8d7c137fbec215f8da286b4a40e53b13d5 (patch) | |
| tree | f9c456717880679c49aec857a1f1c75accb20579 /src/backend/executor | |
| parent | 1346f40b584d8072bdacdf312027c0ef57e4b7c2 (diff) | |
| download | postgresql-0b821b8d7c137fbec215f8da286b4a40e53b13d5.tar.gz postgresql-0b821b8d7c137fbec215f8da286b4a40e53b13d5.zip | |
Add locking around SSL_context usage in libpq
I've been working with Nick Phillips on an issue he ran into when
trying to use threads with SSL client certificates. As it turns out,
the call in initialize_SSL() to SSL_CTX_use_certificate_chain_file()
will modify our SSL_context without any protection from other threads
also calling that function or being at some other point and trying to
read from SSL_context.
To protect against this, I've written up the attached (based on an
initial patch from Nick and much subsequent discussion) which puts
locks around SSL_CTX_use_certificate_chain_file() and all of the other
users of SSL_context which weren't already protected.
Nick Phillips, much reworked by Stephen Frost
Back-patch to 9.0 where we started loading the cert directly instead of
using a callback.
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions