Opened 19 months ago

Last modified 7 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: Applications/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 (4)

comment:3 Changed 9 months 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 7 months ago by arlolra

  • Keywords SRV DNS removed
Note: See TracTickets for help on using tickets.