| From: | Cameron Vogt <cvogt(at)automaticcontrols(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: TLS session tickets disabled? |
| Date: | 2024-08-14 21:59:53 |
| Message-ID: | DM6PR16MB31455B7F25D9A788B1C0EF17AB872@DM6PR16MB3145.namprd16.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Update: I found an old NpgSQL thread at https://github.com/npgsql/npgsql/issues/576 that discusses this issue in more detail. This thread suggests adding "UseSslStream=false" to the connection string. I tested this, and now NpgSQL 4.0.10 works with PostgreSQL 16.4. Unfortunately, I cannot control the connection string Power BI uses to connect to my PostgreSQL database, but I suppose recompiling NpgSQL 4.0.10 with that option disabled by default would work. I've read in a couple places that this issue only occurs when ssl_ca_file is set, and I can confirm that my PostgreSQL server has this. So configuring ssl_ca_file may be important for anyone wishing to reproduce the issue.
I don't know enough about TLS handshakes and session tickets to know where the bug truly lies (PostgreSQL/OpenSSL vs .NET's SslStream).
Cameron Vogt | Software Developer
Direct: 314-756-2302 | Cell: 636-388-2050
1585 Fencorp Drive | Fenton, MO 63026
Automatic Controls Equipment Systems, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2024-08-14 22:28:43 | Re: BUG #18558: ALTER PUBLICATION fails with unhelpful error on attempt to use system column |
| Previous Message | Tomas Vondra | 2024-08-14 17:54:32 | Re: Certain options in pg_upgrade don't seem to work. |