| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Nico Williams <nico(at)cryptonector(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Filip Janus <fjanus(at)redhat(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Subject: | Re: Channel binding for post-quantum cryptography |
| Date: | 2025-10-28 17:34:27 |
| Message-ID: | CAOYmi+nkVOdQM2XgDz1VWPDRj11z-aOcpQJ3m2Sa0jP4rAu_4w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 28, 2025 at 9:46 AM Nico Williams <nico(at)cryptonector(dot)com> wrote:
> RFC 5929 co-author here. We should take this to the IETF TLS WG mailing
> list and update RFC 5929 and the tls-server-end-point registraion to fix
> this.
>
> Options in the case that the certificate's signature algorithm does not
> have a digest associated with it include:
Ah. (Filip, disregard my earlier question about the draft RFC and
sigalgs; I think I understand now. I didn't look closely enough at the
patch before sending.)
> Maybe there are more options still. But we're not likely to solve this
> problem here. This really belongs on the IETF TLS WG mailing list.
+1. (Any immediate takers on the committer side?)
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sami Imseih | 2025-10-28 17:37:10 | Re: [BUG] temporary file usage report with extended protocol and unnamed portals |
| Previous Message | Nathan Bossart | 2025-10-28 17:21:15 | Re: Feature: psql - display current search_path in prompt |