Tor implementation is now changed so tor connection can be set on a per node basis. The tor setting in preferences only affects other http reqest like exchange rate data or opening links from within the app.
Exposed certificate validation on a per node basis
Motivation and Context
Tor & Certificate validation can now be set on a per node basis. This allows switching between a tor and a clearnet node without having to change any settings in the settings menu.
It furthermore allows to connect to a clearnet node while at the same time requesting currency exchange data over tor or work with other tor request. This should fix #383
By exposing certificate validation as a setting on a per node basis, it simplifies node setup in testing environments or more specific setups like connecting with tailscale. Warnings are in place so users do not misuse this function.
How Has This Been Tested?
On my S9
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Description
Motivation and Context
Tor & Certificate validation can now be set on a per node basis. This allows switching between a tor and a clearnet node without having to change any settings in the settings menu. It furthermore allows to connect to a clearnet node while at the same time requesting currency exchange data over tor or work with other tor request. This should fix #383 By exposing certificate validation as a setting on a per node basis, it simplifies node setup in testing environments or more specific setups like connecting with tailscale. Warnings are in place so users do not misuse this function.
How Has This Been Tested?
On my S9
Types of changes
Checklist: