Re: Changing client-side behavior regarding Certificate Revocation Lists (CRL)

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Михаил Купцов <mr(dot)cuptsov2018(at)yandex(dot)ru>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Changing client-side behavior regarding Certificate Revocation Lists (CRL)
Date: 2026-08-25 15:24:44
Message-ID: CAOYmi+knNA+U9uU+HOPASQ2zOsYTZibn=ms3QP5-mCvgC-5jLA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 25, 2026 at 1:08 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> I think a stricter CRL policy would need another trigger.

More fuel for the fire of a .libpqrc, maybe?

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-08-25 15:44:21 Re: Coverage (lcov) failing with inconsistent error in versions 2.x
Previous Message Mario González 2026-08-25 15:10:28 Re: [PATCH] Add support for INSERT ... SET syntax