# tor Published articles for tor. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Snowflake Volunteer open-source app DevFeed: [Snowflake Volunteer open-source app]() Original publisher: [Read original article]() Author: Cláudia Published: 2026-05-13T14:19:29Z Content type: article Language: en Sources: [Blog - Bloco]() Topics: [tor](), [Android](), [Virtual Private Network](), [Open Source](), [proxy](), [Internet](), [Protocol (disambiguation)]() Tags: [android](), [app](), [apps](), [automatically](), [design](), [development](), [network](), [open-source](), [proxy](), [tor]() ### AI overview Snowflake Volunteer is an open-source Android app that lets people run a Snowflake proxy to help others access the Tor network where it is blocked. The article explains installation and configuration options, including limiting operation to Wi-Fi or charging, and points to the source repository, bug reporting, feature requests, and translation work. ### Source excerpt Snowflake Volunteer is an open-source app that helps others reach the Tor network in places where Tor is blocked. It turns your phone into an anonymous Volunteer proxy, without you having to worry about the technical stuff. Similar to VPNs, which help users bypass Internet censorship, the Snowflake protocol disguises Internet activity as if someone were making a video or voice call, making it less detectable to Internet censors. ## Using OpenTofu/Terraform to create a disposable Tails virtual machine DevFeed: [Using OpenTofu/Terraform to create a disposable Tails virtual machine]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2025-06-22T06:37:00Z Content type: tutorial Language: en Sources: [stafwag Blog]() Topics: [opentofu](), [Infrastructure as code](), [virtualization](), [gnu linux]() Tags: [fosdem](), [infrastructure-as-code](), [libvirt](), [linux](), [linux-foundation](), [open-source](), [opentofu](), [tails](), [terraform](), [tor](), [virtual-machine](), [virtualization]() ### AI overview This tutorial explains how OpenTofu and Terraform can provision disposable environments and presents a Terraform/OpenTofu module for creating a virtual machine running the latest Tails version on libvirt. It also notes security considerations for running Tails in a virtual machine. ### Source excerpt OpenTofu Terraform or OpenTofu (the open-source fork supported by the Linux Foundation) is a nice tool to setup the infrastructure on different cloud environments. There is also a provider that supports libvirt. https://github.com/dmacvicar/terraform-provider-libvirt If you want to get started with OpenTofu there is a free training available from the Linux foundation: https://training.linuxfoundation.org/express-learning/getting-started-with-opentofu-lfel1009/ I also joined the talk about OpenTofu and Infrastructure As Code, in general, this year in the Virtualization and Cloud Infrastructure DEV Room at FOSDEM this year: https://fosdem.org/2025/schedule/event/fosdem-2025-6057-the-iac-tooling-multiverse-and-the-future-of-iac/ ## Running a Tor relay with Docker DevFeed: [Running a Tor relay with Docker]() Original publisher: [Read original article]() Published: 2015-08-23T16:02:01Z Content type: tutorial Language: en Sources: [Jessie Frazelle]() Topics: [Docker](), [Dockerfile](), [container](), [Docker Container](), [Docker Image](), [hosting](), [Linux](), [Network]() Tags: [bridge](), [docker](), [docker-container](), [docker-image](), [exit-node](), [hosting](), [linux](), [network](), [tor]() ### AI overview A tutorial on running Tor bridge, middle, and exit relays in Docker containers. It covers creating a minimal Alpine-based Docker image with separate Tor configurations, running each relay type, and checking whether an exit node has registered. ### Source excerpt This post is part two of what will be a three part series. If you missed it part one was How to Route Traffic through a Tor Docker container. I figured it was important, if you are going to be a tor user, to document how you can help the Tor community by hosting a Tor relay. And guess what? You can use Docker to do this! There are three types of relays you can host, a bridge relay, a middle relay, and an exit relay. Exit relays tend to be the ones recieving take down notices because the IP is the one the public sees traffic from Tor as. A great reference for hosting an exit node can be found here blog.torproject.org/blog/tips-running-exit-node-minimal-harassment. But I will go over how to host each from a Docker container. My example will have a reduced exit policy and limit which ports you are willing to route traffic through. If you don't want to host an exit node, host a middle relay instead! And if you want your relay not publically listed in the network then host a bridge. Creating the base image I have created a Docker image jess/tor-relay from this Dockerfile. Feel free to create your own image with the following Dockerfile: FROM alpine:latest # Note: Tor is only in testing repo RUN apk update && apk add \ tor \ --update-cache --repository http://dl-3.alpinelinux.org/alpine/edge/testing/ \ && rm -rf /var/cache/apk/* # default port to used for incoming Tor connections # can be changed by changing 'ORPort' in torrc EXPOSE 9001 # copy in our torrc files COPY torrc.bridge /etc/tor/torrc.bridge COPY torrc.middle /etc/tor/torrc.middle COPY torrc.exit /etc/tor/torrc.exit # make sure files are owned by tor user RUN chown -R tor /etc/tor USER tor ENTRYPOINT [ "tor" ] As you can see we are copying 3 different torrc's into the container. One for each a bridge, middle, and exit relay. I used alpine linux because it is super minimal. The size of the image is 11.52MB! Crazyyyyyyy! Running a bridge relay A bridge relay is not publically listed as part of the Tor network. Th ## How to Route Traffic through a Tor Docker container DevFeed: [How to Route Traffic through a Tor Docker container]() Original publisher: [Read original article]() Published: 2015-06-20T23:40:01Z Content type: tutorial Language: en Sources: [Jessie Frazelle]() Topics: [Docker Container](), [Docker](), [container](), [Dockerfile](), [Bash](), [networking]() Tags: [bash](), [commands](), [docker](), [docker-container](), [how-to](), [routing](), [tor]() ### AI overview A tutorial showing how to route a host's traffic through a Tor Docker container using Docker networking and iptables rules. It covers running the jess/tor image, checking routing through Tor, and configuring DNS and TCP redirection while allowing selected clearnet destinations. ### Source excerpt This blog post is going to explain how to route traffic on your host through a Tor Docker container. It's actually a lot simplier than you would think. But it involves dealing with some unsavory things such as iptables. Run the Image I have a fork of the tor source code and a branch with a Dockerfile. I have submitted upstream... we will see if they take it. The final result is the image jess/tor, but you can easily build locally from my repo jessfraz/tor. So let's run the image: $ docker run -d \ --net host \ --restart always \ --name tor \ jess/tor Easy right? I can already hear the haters, "blah blah blah net host". Chill out, the point is to route all our traffic duhhhh so we may as well, otherwise would need to change / overwrite some of Docker's iptables rules, and really who has time for that shit... You do? Ok make a PR to this blog post. Routing Traffic Contain yourselves, I am about to throw down some sick iptables rules. #!/bin/bash # Most of this is credited to # https://trac.torproject.org/projects/tor/wiki/doc/TransparentProxy # With a few minor edits # to run iptables commands you need to be root if [ "$EUID" -ne 0 ]; then echo "Please run as root." exit 1 fi ### set variables # destinations you don't want routed through Tor _non_tor="192.168.1.0/24 192.168.0.0/24" # get the UID that Tor runs as _tor_uid=$(docker exec -u tor tor id -u) # Tor's TransPort _trans_port="9040" _dns_port="5353" ### set iptables *nat iptables -t nat -A OUTPUT -m owner --uid-owner $_tor_uid -j RETURN iptables -t nat -A OUTPUT -p udp --dport 53 -j REDIRECT --to-ports $_dns_port # allow clearnet access for hosts in $_non_tor for _clearnet in $_non_tor 127.0.0.0/9 127.128.0.0/10; do iptables -t nat -A OUTPUT -d $_clearnet -j RETURN done # redirect all other output to Tor's TransPort iptables -t nat -A OUTPUT -p tcp --syn -j REDIRECT --to-ports $_trans_port ### set iptables *filter iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT # allow clearnet access for hosts in ## Using Tor to Circumvent Country Origin Restrictions DevFeed: [Using Tor to Circumvent Country Origin Restrictions]() Original publisher: [Read original article]() Published: 2014-02-28T03:23:11Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [tor]() Tags: [article](), [exit-node](), [location](), [tor](), [using]() ### AI overview This article explains how to use Tor by forcing traffic through an exit node in a specific location to circumvent country-based content restrictions. ### Source excerpt Sometimes content hosted in one country is restricted from viewing in another. This article describes how you can use Tor to circumvent such restrictions by forcing the use of an exit node in a specific location." ## tor: generowanie milszej nazwy dla hidden service DevFeed: [tor: generowanie milszej nazwy dla hidden service]() Original publisher: [Read original article]() Author: Tom Published: 2013-09-09T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [tor]() Tags: [regexp](), [tor]() ### AI overview The author describes exposing a website through a Tor hidden service and finding Shallot, which generates hidden-service names until one matches a specified regular expression. ### Source excerpt Chcąc pobawić się tor'em postanowiłem udostępnić jedna z moich stron z wykorzystaniem mechanizmu hidden service. Nie spodobał mi się jedynie sposób generowania nazw, które były mało opisowe - ale najwidoczniej nie mnie jednemu, bo szybko namierzyłem Shallot external link , który generuje kolejne nazwy aż trafi na pasującą do zadanego regexp'a. ## Fun with The Great Firewall DevFeed: [Fun with The Great Firewall]() Original publisher: [Read original article]() Author: Marek Published: 2013-07-10T22:00:00Z Content type: opinion Language: en Sources: [Marek Majkowski]() Topics: [Firewall](), [tor](), [TCP/IP]() Tags: [firewall](), [iptables](), [payload](), [port](), [servers](), [ssl](), [tcp-ip](), [tor]() ### AI overview The article describes observations of how China's Great Firewall probes and blocks Tor bridges. It reports that detected Tor bridges may have their IP-and-port tuples blocked for hours, while later probing behavior appeared to vary over time and was not fully understood. ### Source excerpt Fun with The Great Firewall I was playing with the Tor Project and decided to understand how the Chinese block Tor servers. Philipp Winter wrote an amazing paper on that subject. He noticed The Great Firewall of China is actively scanning services and if it detects a Tor bridge it blocks the ip:port tuple for a few hours. TCP/IP When a port gets censored "ACK" packets are dropped by the GFW. Most importantly and . ## Running a Tor relay / node / server on Ubuntu DevFeed: [Running a Tor relay / node / server on Ubuntu]() Original publisher: [Read original article]() Author: Graham King Published: 2011-03-01T06:29:04Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Ubuntu](), [Internet](), [Server](), [browser](), [public key](), [email](), [Debian](), [IRC]() Tags: [browser](), [debian](), [email](), [irc](), [public-key](), [running](), [server](), [society](), [software](), [tor](), [ubuntu]() ### AI overview A tutorial on running a Tor relay on Ubuntu or Debian. It covers installation, repository setup, relay configuration, bandwidth throttling, exit-relay policies, and port blocking considerations. ### Source excerpt Empower anonymity: Run a Tor relay and make a difference.