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-25 02:00:49 |
Message-ID: | 20200825.110049.765607776821346295.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Mon, 24 Aug 2020 21:49:40 -0400, Bruce Momjian <bruce(at)momjian(dot)us> wrote in
> > > Are you saying we should _require_ clientcert=verify-full when 'cert'
> > > authentication is used? I don't see the point of that --- I just
> > > updated the docs to say doing so was duplicate behavior.
> >
> > I don't suggest changing the current behavior. I'm saying it is the
> > way it is working and we should correctly error-out that since it
> > doesn't work as specified.
Sorry, I mistead you. I don't suggest verify-full is needed for cert
authentication. I said we should just reject the combination
cert+veriry-ca.
> Uh, I don't understand what 'combination the same way with
> "cert"+"no-verify"'. Right now, cert with no clientcert/verify line
> works just fine. Is "no-verify" something special? Are you saying it
> is any random string that would generate an error?
It was delimited as "We should reject (that)" "that combination
(=cert+ferify-ca)" "the same way(=error-out)" "with cert+no-verify".
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2020-08-25 02:06:45 | Re: "cert" + clientcert=verify-ca in pg_hba.conf? |
Previous Message | Bruce Momjian | 2020-08-25 01:49:40 | Re: "cert" + clientcert=verify-ca in pg_hba.conf? |