Gestern noch Snowflake im Heimnetz, heute eine obfs4 Bridge auf dem 'richtigen' Server installiert:
https://community.torproject.org/relay/setup/bridge/debian-ubuntu/

#tor #debian #obfs4 #server #privacy #freedom #censorship #zensur #überwachung

Tor Project | Debian / Ubuntu

Defend yourself against tracking and surveillance. Circumvent censorship. | Debian / Ubuntu

@nono2357 I'm running an #obfs4 proxy on a VPS & followed this. It's amazing how many attempted logins get blocked with #fail2ban. SSH Key Authentication is also amazing.
Request obfs4 bridges via email.
Use moat for automatic retrieval.
Verify fingerprints before connecting.
#Tor #Bridges #Obfs4 #Censorship

We've been hard at work the past few months!

1. Leaving the Westin datacenter in downtown Seattle and moving on from expensive co-location

2. Moving our gear to Fremont, California

3. Bringing on board a few new Advisory Board members, including @whil who has been an incredible help deploying our #Proxmox infrastructure, and @alexhaydock who has been instrumental in deploying our new #Ansible infra, new recursive #DNS resolution infra, and new #Tor exit relays in California! See: https://infosec.exchange/@alexhaydock/114687688286984967 with more updates to follow

4. Installing new co-location with some older low-power systems in Amsterdam for our self-hosted #ActivityPub infra @ https://disobey.net, where we just moved our #Mastodon profile to!

5. Deploying a new #XMTP node @ https://xmtp.disobey.net, and testing a new #DeltaChat relay!

6. Deploying some new #obfs4 private bridges for use in a country who's conducting heavy internet surveillance and censorship, blocking access to @torproject

and today is our birthday!!! we're 8 years old today ^_^ stay tuned for more updates to come!

Alex Haydock (@[email protected])

Attached: 1 image We deployed 24x new Tor exit relays today for @[email protected] ! 🧅 I'm excited to post (or maybe talk) about our deployment architecture soon. We're deploying relays as diskless VMs that each boot from a single EFI binary. No logging, no persistence. Pretty much just the Tor daemon. https://metrics.torproject.org/rs.html#search/family:186F046D8895E13626B363B879BD15F38A52C6BC

Infosec Exchange

I am running a #TorProject #obfs4 relay on a #Debian VPS.

#Uptime

So I moved my #Tor #Obfs4 Relay from my home LAN to a VPS. I was not getting great bandwidth from Bell Aliant, who I suspect were throttling my connection. My advertised bandwidth is now 1.04 MiB/s, a vast improvement from being on my LAN.
So I decided to abandon hosting an #obfs4 bridge on my home network & am investing in a VPS service for $11.00 USD a year.
Rebuilt #obfs4 bridge is now back online!

@tails_live @tails @torproject plus support for meek, snowflake, webtunnel and non-#obfs4 #Bridges seems missing in #Tails.

Cuz to this day I've to yet see an IPv4-#webtunnel #bridge

#meek #snowflake #Tor #privacy #InternetCensorship

The Tor Project | Privacy & Freedom Online

Defend yourself against tracking and surveillance. Circumvent censorship.

So I had been running my #OBFS4 Relay behind my Bell Fiber modem w/o issue & decided to move it behind my #UniFi UXG Lite gateway.

I set the server (running Debian) to DHCP & created the port forwarding rules on the UXG. It looked OK but I started to get the "Your server has not managed to confirm reachability for its ORPort(s) at xxx.xxx.xxx.xxx:ZZZZ.

I troubleshot the issue with my buddy Julien & we found the issue was with Home Hub 4000 (HH4K) and the Advanced DMZ. Even though the UXG was showing a public IP on the WAN Port and the HH4K was showing that the port the UXG is plugged into is configured for Advanced DMZ, traffic was not being passed back & forth.

I disabled the HH4K DMZ & reserved a DHCP IP for the UXG & created a port forwarding rule for the TOR ports on the HH4K to the UXG. Then on the UXG, I created port forwarding rules from the WAN IP, which is now an internal IP, to the Relay server.

After a reboot, things came back online.