Opened 3 years ago
Last modified 14 months ago
#17461 new defect
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 (5)
comment:1 Changed 3 years ago by
comment:2 Changed 3 years ago by
In Instantbird this is https://bugzilla.mozilla.org/show_bug.cgi?id=787369
comment:3 follow-up: 5 Changed 2 years ago by
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 2 years ago by
| Keywords: | SRV DNS removed |
|---|
comment:5 Changed 14 months ago by
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
https://bugzilla.mozilla.org/show_bug.cgi?id=14328