security enhancement needed: add Tor support on a per-account basis

Diligent streetwise users run Orbot and use Netguard to force traffic from selected apps over Tor. That works fine for those who only have a regular Jami account. But what happens if a user adds a SIP account? Most SIP services are not on the ball about security and SIP traffic is generally sent in-the-clear. This means when Jami is forced over Tor and a user adds a SIP account, their account creds and conversation is exposed to the Tor exit node. Yikes! This actually happened to me because I didn’t think that through before adding the SIP account.

The current Jami app design does not even acknowledge the existence of Tor or proxies, which forces users to configure Jami traffic and SIP traffic to travel the same route. Jami traffic should typically go over Tor but SIP traffic should not (unless the SIP service supports TLS).

Proposal: every account profile should have a proxy setting.