From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Move OpenSSL random under USE_OPENSSL_RANDOM |
Date: | 2020-11-19 09:25:20 |
Message-ID: | 8293CD7B-D36B-4E82-B876-5BD5980A77CE@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 19 Nov 2020, at 04:34, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Wed, Nov 18, 2020 at 10:43:35AM +0100, Daniel Gustafsson wrote:
>> While it does simplify configure.ac, I'm just not a fan of the strict ordering
>> which is required without the labels even implying it. But that might just be
>> my personal preference.
>
> I just looked at that, and the attached seems more intuitive to me.
Ok. I would add a strongly worded comment about the importance of the ordering
since that is now crucial not to break.
-#ifdef USE_WIN32_RANDOM
+#ifdef WIN32
#include <wincrypt.h>
#endif
-#ifdef USE_WIN32_RANDOM
+#ifdef WIN32
/*
* Cache a global crypto provider that only gets freed when the process
* exits, in case we need random numbers more than once.
@@ -39,7 +39,7 @@
static HCRYPTPROV hProvider = 0;
#endif
This will pull in headers and define hProvider for all Windows builds even if
they use OpenSSL, but perhaps that doesn't matter?
cheers ./daniel
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2020-11-19 09:27:18 | Re: ResourceOwner refactoring |
Previous Message | Ajin Cherian | 2020-11-19 09:22:11 | Re: [HACKERS] logical decoding of two-phase transactions |