@shelldozer
Its another drone-training website for Screw-gle.

Its fine, we know #Brave is sub-optimal and to use #TorBrowser. As per #TailOS, we also know TorBrowser performs better whenever #uBlock add-on is used.

We recommend implementing #TransparentTorification, including for #DNS ie. ones firewall should redirect all port 53 DNS requests to Tor's 5353 port. One may need to find creative ways to set the time, but it's better than not doing #torification.
@lproven @anomalocaris

@Rob @mconley @gunchleoc
Yes, even better by using TorBrowser in Safest Mode you are helping defeat a lot of bad actors, too. Not just 'Screw'-gle.

We say #TransparentTorification, ie. putting all your traffic through Tor, is fine too and for heaven's sake use #I2P, especially for #torrenting.

Onion all the things — if your bank doesn't like it, get them to send you out a cheque book. They will **love** that

#OnionMaximalist #makeJavascriptOptional

@jens
DoH goes to a clearnet IP address, and port 443, but #TransparentTorification is supposed to take any new connection not going through Tor and put it through Tor, no?

So unless the application itself, in this case #DoH, outs your IP address, you should be safe.

@JulianOliver

We've identified a flaw in the #ArchLinux Wiki on #TransparentTorification.

If the #DNS queries are sent direct to your #router then the following rule/line in their #iptables setup will permit that **before** the DNS query is redirected to 5353.

--ipv4 -A OUTPUT -d 192.168.0.0/16 -j RETURN

The above line must be moved down two lines, to below the "udp --dport 53" line.

See https://wiki.archlinux.org/title/Tor#Transparent_Torification

Please fix ASAP if you have access.

#transparentProxy #tor #archLinuxWiki