Re: Direct SSL connection and ALPN loose ends

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Direct SSL connection and ALPN loose ends
Date: 2024-07-26 14:34:06
Message-ID: b139b3c2-0912-4e40-9458-71ce3516c427@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 17/06/2024 21:33, Andres Freund wrote:
> If provided with the necessary key information, wireshark can decode TLS
> exchanges when using sslnegotiation=postgres but not with direct. Presumably
> it needs to be taught postgres' ALPN id or something.

I opened https://gitlab.com/wireshark/wireshark/-/merge_requests/16612
to fix that in the wireshark pgsql protocol dissector.

--
Heikki Linnakangas
Neon (https://neon.tech)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2024-07-26 14:38:03 Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Previous Message Michał Kłeczek 2024-07-26 14:33:29 Re: DRAFT: Pass sk_attno to consistent function