Opened 5 years ago

Closed 2 years ago

#17461 closed defect (wontfix)

Client does not find responsible jabber servers (not parsing SRV DNS records)

Reported by: flowolf Owned by:
Priority: Medium Milestone:
Component: Archived/Tor Messenger Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Jabber servers can be defined using SRV records. (​http://prosody.im/doc/dns, ​http://wiki.xmpp.org/web/SRV_Records)

e.g. the nic max@… can have xmpp servers that do not listen on the example.com servers but on xmpp.example.com. These would be defined in a SRV record, see links.

It seems the client does not check for these records, as it tries to connect to example.com directly.

current workaround is to define xmpp.example.com as server manually in the advanced options.

Child Tickets

Change History (6)

comment:3 Changed 4 years ago by arlolra

IB closed that bug (787369) but they did it by bypassing the remote dns config, which is dangerous for us. We should be very careful here when moving to ESR 52. I think there's a switch to turn it off though, which is helpful.

See ​https://bugzilla.mozilla.org/show_bug.cgi?id=787369#c66

comment:4 Changed 4 years ago by arlolra

Keywords: SRV DNS removed

comment:5 in reply to:  3 Changed 3 years ago by arlolra

Replying to arlolra:

IB closed that bug (787369) but they did it by bypassing the remote dns config, which is dangerous for us. We should be very careful here when moving to ESR 52. I think there's a switch to turn it off though, which is helpful.

Disabled in, ​https://gitweb.torproject.org/tor-messenger-build.git/commit/?id=d47648c8a55ad5d2419827aff7461688cc026c41

comment:6 Changed 2 years ago by traumschule

Resolution: → wontfix
Status: new → closed

<+sukhe> hello. yes, I think it's fine to close the tickets. thanks for doing what we should done earlier :)

Note: See TracTickets for help on using tickets.