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

Dear Hackers,

I would like to propose a different approach regarding the client side behavior in terms of working with the list of revoked certificates.


The problem that was discovered is that if a user, using psql, accidentally specifies an incorrect path to a crl file or crl directory, the client part of Postgres ignores the user's error and connects the client to the database whose certificate the client would, in theory, want to check whether the database server certificate has been revoked.

Regards,

- Michael