On Tue, Oct 28, 2025 at 9:46 AM Nico Williams <[email protected]> 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
