From: | George MacKerron <george(at)mackerron(dot)co(dot)uk> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Making sslrootcert=system work on Windows psql |
Date: | 2025-04-02 14:15:24 |
Message-ID: | B831248A-3285-4A0D-BA48-1A297AAC435C@mackerron.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 2 Apr 2025, at 14:39, George MacKerron <george(at)mackerron(dot)co(dot)uk> wrote:
> But happily, I don’t think we need to choose. Can’t we just use the Windows system store if neither of the relevant environment variables is set?
Thinking about this a little more, I guess the remaining concern is about people on Windows compiling their own psql from source, using an OpenSSL build that has a meaningful OPENSSLDIR baked in.
I guess that might suggest we should make the "org.openssl.winstore:" code path something users can opt out of (or even, for maximum backwards-compatibility, opt in to) at compile-time.
My preference would be for "org.openssl.winstore:" to be the compile-time default, though, because the option is called sslrootcert=system and it’s documented as using “the system’s trusted CA roots” (not sslrootcert=openssldir or documented as using OpenSSL’s default CA roots).
From | Date | Subject | |
---|---|---|---|
Next Message | Alena Rybakina | 2025-04-02 14:33:43 | Re: Replace IN VALUES with ANY in WHERE clauses during optimization |
Previous Message | jian he | 2025-04-02 13:51:31 | Re: Support NOT VALID / VALIDATE constraint options for named NOT NULL constraints |