RFC 9266: Channel Bindings for TLS 1.3 support

[Neustradamus]

Dear @sunng87,

Can you add the support of RFC 9266: Channel Bindings for TLS 1.3?

• https://datatracker.ietf.org/doc/html/rfc9266

Channel Bindings for TLS: https://datatracker.ietf.org/doc/html/rfc5929

• XEP-0388: Extensible SASL Profile: https://xmpp.org/extensions/xep-0388.html
• XEP-0440: SASL Channel-Binding Type Capability: https://xmpp.org/extensions/xep-0440.html
• XEP-0474: SASL SCRAM Downgrade Protection: https://xmpp.org/extensions/xep-0474.html
• XEP-0480: SASL Upgrade Tasks: https://xmpp.org/extensions/xep-0480.html

Little details, to know easily:

• tls-unique for TLS =< 1.2 (RFC5929)
• tls-server-end-point =< 1.2 + 1.3 (RFC5929)
• tls-exporter for TLS = 1.3 (RFC9266)

After the jabber.ru MITM, it is time to add it:

• https://notes.valdikss.org.ru/jabber.ru-mitm/
• https://snikket.org/blog/on-the-jabber-ru-mitm/
• https://www.devever.net/~hl/xmpp-incident
• https://blog.jmp.chat/b/certwatch/certwatch

Thanks in advance.

Linked to:

• Channel Binding: State of Play scram-sasl/info#1
• SASL/SCRAM authentication #26
• SCRAM Channel binding support #27
• SCRAM-SHA256-PLUS with tls-server-end-point channel binding #31

[sunng87]

@Neustradamus Thank you for the information. Do you know if this is supported in original postgresql? How about its support on client side?

I will leave this open for someone to pick up, or when I get time for myself

[Neustradamus]

@sunng87: After my original request here:

• https://www.postgresql.org/message-id/PA4PR01MB992243D329F60932DE56BAAFCB969@PA4PR01MB9922.eurprd01.prod.exchangelabs.com

@michaelpq has done: https://www.postgresql.org/message-id/YwxWWQR6uwWHBCbQ%40paquier.xyz

But currently, I do not see tls-exporter in main code: https://github.com/postgres/postgres

• https://github.com/search?q=org%3Apostgres+tls-exporter&type=code
• https://github.com/search?q=org%3Apostgres+tls-server-end-point&type=code
• https://github.com/search?q=org%3Apostgres+tls-unique&type=code

[michaelpq]

@michaelpq has done: https://www.postgresql.org/message-id/YwxWWQR6uwWHBCbQ%40paquier.xyz

But currently, I do not see tls-exporter in main code: https://github.com/postgres/postgres

There is currently no active patch to add tls-exporter to PostgreSQL. The last thread about this matter was stuck on the point about channel binding negotiation between the client and the backend, and I recall that the RFCs don't tell much about that except "you can do as you wish".

[sunng87]

Got it. I will be waiting for a wider adoption of this feature to ensure typical postgres clients will work for pgwire.

[Neustradamus]

@michaelpq: Have you progressed on tls-exporter and PostgreSQL?

Thanks in advance.

[michaelpq]

@michaelpq: Have you progressed on tls-exporter and PostgreSQL?

In short, no.

[Neustradamus]

@michaelpq: For your information, if you have not seen:

@jas4711 has published this message on Kitten IETF ML:

• https://mailarchive.ietf.org/arch/msg/kitten/zpesKSHsiuy1RvhPlbSUGajLbKQ/

It will not be in GNU SASL too:

• https://gitlab.com/gsasl/gsasl/-/issues/13

@simo5 has done this comment:

• https://mailarchive.ietf.org/arch/msg/kitten/-hhno2IUJQwXOyJT3-CTaKxoOuA/