Re: TLS session tickets disabled?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Cameron Vogt <cvogt(at)automaticcontrols(dot)net>, "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-16 14:44:25
Message-ID: 742117.1723819465@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
> On 15 Aug 2024, at 19:52, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
>>> I'm getting the feeling that this is our bug, and that we should be
>>> using both SSL_OP_NO_TICKET (for TLSv1.2) and SSL_CTX_set_num_tickets
>>> (for TLSv1.3). I don't see any indication in the docs or source that
>>> the latter does anything for 1.2.

> The attached, backpatched all the way, should be the correct fix. Sorry for
> the mess =(

Can we verify that this fixes the originally-reported problem?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2024-08-16 15:26:58 Re: BUG #18348: Inconsistency with EXTRACT([field] from INTERVAL);
Previous Message Marcin Barczyński 2024-08-16 08:29:15 REINDEX INDEX pg_catalog.pg_default_acl_role_nsp_obj_index stuck waiting for transaction from the future in PG 13.16