| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | digoal(at)126(dot)com |
| Subject: | BUG #16505: ssl_crl_file bug? |
| Date: | 2020-06-19 11:58:35 |
| Message-ID: | 16505-201e8f9d7734d3cd@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16505
Logged by: Zhou Digoal
Email address: digoal(at)126(dot)com
PostgreSQL version: 12.3
Operating system: CentOS 7.7 x64
Description:
HI,
when i set client's cert content into dbserver's ssl_crl_file, cann't
connect, its correct.
but when i make a new client cert, and use the new cert also cann't connect
to dbserver.
is there a bug?
details in:
https://github.com/digoal/blog/blob/master/202006/20200619_01.md
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-06-19 14:09:06 | Re: BUG #16504: Wrapping query in EXISTS() causes sequential scans of tables |
| Previous Message | Bruce Momjian | 2020-06-19 11:37:23 | Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match |