#transparenttorification — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #transparenttorification, aggregated by home.social.
-
@aktivismoEstasMiaLuo Site is #CloudGlare.
AVOID
Its easy to forget to check. Best is to have a checking reflex. We say tunnel #DNS through #Tor (port 5353 is typical for this, and on linux you can easily setup this with #iptables). A person can optionally do full #TransparentTorification where *all* traffic goes through Tor but is not needed here.
Next setup #DFCA firewall to block '#DigitalFeudalism'.
Now just expose and block any #technoFash with command:
wget https;//example.com
Ta-da!
-
@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 -
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.