Open
Bug 1889865
Opened 2 years ago
Updated 2 years ago
Allow TCPSocket to use routed transport
Categories
(Core :: DOM: Networking, enhancement, P3)
Core
DOM: Networking
Tracking
()
NEW
People
(Reporter: mkmelin, Unassigned)
References
Details
(Whiteboard: [necko-triaged])
nsIRoutedSocketTransportService allow(ed) for the case of XMPP using SRV records where there is mismatch on the certificate - if user specified hostname example.com and SRV says im.example.com, certificate should be checked against example.com - see RFC 3920.
XMPP uses a custom old homegrown socket implementation hooking up to networking internals.
tlsSocketControl.StartTLS() does not really work anymore since you end up on wrong thread.
This would preferably use TCPSocket instead, but the missing part is lack of routed transport for the case mentioned above.
Comment 1•2 years ago
|
||
I'm not sure how much time the Necko team can dedicate to TCPSocket.
I'm going to put this in our backlog, but we're happy to review patches anyone might want to contribute.
Severity: -- → S3
Priority: -- → P3
Whiteboard: [necko-triaged]
You need to log in
before you can comment on or make changes to this bug.
Description
•