From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | bruce(at)momjian(dot)us |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: "cert" + clientcert=verify-ca in pg_hba.conf? |
Date: | 2020-08-31 08:56:58 |
Message-ID: | 20200831.175658.2102256886277891280.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello, Bruce.
At Thu, 27 Aug 2020 15:41:40 -0400, Bruce Momjian <bruce(at)momjian(dot)us> wrote in
> > My point here is just "are we OK to remove it?"
>
> Yes, in PG 14. Security is confusing enough, so having a mis-named
> option that doesn't do anything more than just not specifying clientcert
> is not useful and should be removed.
Ok, this is that. If we spcify clientcert=no-verify other than for
"cert" authentication, server complains as the following at startup.
> LOG: no-verify or 0 is the default setting that is discouraged to use explicitly for clientcert option
> HINT: Consider removing the option instead. This option value is going to be deprecated in later version.
> CONTEXT: line 90 of configuration file "/home/horiguti/data/data_noverify/pg_hba.conf"
And, cert clientcert=verifry-ca (and no-verify) is correctly rejected.
> LOG: clientcert accepts only "verify-full" when using "cert" authentication
I once I thought that the deprecation message should e WARNING but
later I changed my mind to change it to LOG unifying to surrounding
setting error messages.
I'm going to register this to the coming CF.
regrds.
--
Kyotaro Horiguchi
NTT Open Source Software Center
Attachment | Content-Type | Size |
---|---|---|
0001-Prepare-for-deprecating-no-verify-for-clientcert.patch | text/x-patch | 3.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2020-08-31 09:03:02 | Re: Is it worth accepting multiple CRLs? |
Previous Message | Jakub Wartak | 2020-08-31 08:49:54 | Re: Handing off SLRU fsyncs to the checkpointer |