Re: TLS session tickets disabled? - Mailing list pgsql-bugs

From Tom Lane
Subject Re: TLS session tickets disabled?
Date
Msg-id 45862.1723572334@sss.pgh.pa.us
Whole thread Raw
In response to TLS session tickets disabled?  (Cameron Vogt <cvogt@automaticcontrols.net>)
List pgsql-bugs
Cameron Vogt <cvogt@automaticcontrols.net> writes:
> I recently updated one of my PostgreSQL databases to 16.4. Since updating, I am unable to refresh Power BI reports
thatrely on the database. The error message in my PostgreSQL server's log file is "could not accept SSL connection:
sessionid context uninitialized". I looked up the error message and found my issue in another mailing list:
https://www.postgresql.org/message-id/CADT4RqBU8N-csyZuzaook-c795dt22Zcwg1aHWB6tfVdAkodZA%40mail.gmail.com.
> After reading the old thread, it looks like the resolution was to make the PostgreSQL server pass SSL_OP_NO_TICKET to
SSL_CTX_set_options.I believe the 16.4 update has resurrected this issue. In the 16.4 release notes, I found a bullet
pointthat says: 

> "Disable creation of stateful TLS session tickets by OpenSSL.
> This avoids possible failures with clients that think receipt of a session ticket means that TLS session resumption
issupported." 

> Would it be possible to get this change reverted in the next update?

What is your argument that it's not the client that is broken?
AFAIK, it should not be requiring a session ticket to exist.

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18582: fixed range of search for empty slot in SLRU
Next
From: Alvaro Herrera from 2ndQuadrant
Date:
Subject: Re: BUG #18559: Crash after detaching a partition concurrently from another session