Tor: Difference between revisions
imported>Onny mNo edit summary |
imported>Onny Add tips and tricks |
||
| Line 61: | Line 61: | ||
An alternative approach is use both a wrapper and built-in proxy support. This way, if the application's proxy support fails, the connection is likely to be caught by the wrapper and if you run the application without the wrapper by mistake, the connections are still likely to be proxied. | An alternative approach is use both a wrapper and built-in proxy support. This way, if the application's proxy support fails, the connection is likely to be caught by the wrapper and if you run the application without the wrapper by mistake, the connections are still likely to be proxied. | ||
== | == KDE == | ||
In KDE, proxy server configuration is set for all applications centrally. You should set the SOCKS proxy to Tor's default SOCKS port (127.0.0.1:9050), and set the HTTP proxy to Privoxy (127.0.0.1:8118). | In KDE, proxy server configuration is set for all applications centrally. You should set the SOCKS proxy to Tor's default SOCKS port (127.0.0.1:9050), and set the HTTP proxy to Privoxy (127.0.0.1:8118). | ||
| Line 79: | Line 79: | ||
= Tips and tricks = | = Tips and tricks = | ||
== | == Sandboxing == | ||
You can also run the [[Tor Browser in a Container]]. | You can also run the [[Tor Browser in a Container]]. | ||
Alternativley Tor can be configured together with the [[Firejail#Torify_application_traffic|Firejail]] sandboxing solution. | |||
== Faster reconnects on network switch == | |||
Using [[networkd-dispatcher]] it is possible to restart the Tor daemon every time network reconnect is performaed. This avoids having to wait for Tor network timeouts and reastablishes a new connection faster. | |||
[[Category:Configuration]] | [[Category:Configuration]] | ||
[[Category:Security]] | [[Category:Security]] | ||