iuviWhat alternative bridges can be used if #webtunnel and #snowflake fails to work with #tor in my country?
The New Oil#GetBridgesBot now provides #webtunnel bridges
Russian Citizens, rejoice! GetBridgesBot now provides webtunnel bridges
After a rather alarming period of downtime, the telegram bot by the Tor Project: GetBridgesBot was updated and now has an option to request webtunnel bridges, which are much better at bypassing censorship than obfs4. From The Tor Project’s blog[source]: WebTunnel is a censorship-resistant pluggable transport designed to mimic encrypted web traffic (HTTPS) inspired by HTTPT. It works by wrapping the payload connection into a WebSocket-like HTTPS connection, appearing to network observers as an...
GusPSA: #tor webtunnel bridge operator: if you're using our official docker image, please check if the container is running after yesterday upgrade. #webtunnel #docker
[tor-relays] [bridge operators] Fix required for WebTunnel docker bridges
Hello bridge operators, During yesterday's upgrade of our WebTunnel docker image, some bridges stopped working due to an operating system issue[1]. Only WebTunnel operators using our official Docker image are affected. If your bridge is affected and you don’t apply this fix, it will remain non-functional and users will not be able to connect. You need to take action now! ### How to check if your bridge is affected Run the command: `docker ps` If your WebTunnel container is stuck in a r...
暗网下
atari
Kevin Karhan 
@torproject Q: I wish there was a similar tool test #Bridges, as https://bridges.torproject.org/scan/ is not that good and I don't want to hammer it with dozens of addresses, cuz at best that's quite antisocial if not possibly trigger responses assuming this is an intelligence gathering operation.
- Ideally sone standalone binary that one can just give a list of #TorBridge|s in a text file (similar to the way one can just past them in at #TorBrowser) would help.
I.e.
bridgetest -v4 obfs4 203.0.113.0:80 …
bridgetest -v6 webtunnel [2001:DB8::1]:443 …
bridgetest -list ./tor.bridges.list.private.tsv
- But maybe #onionprobe already does that. In that case please tell me to "#RTFM!"…
Similarly there needs to be a more granular way to request #TorBridges from #BridgeDB (as it's basically impossible to get #IPv4 #Webtunnel addresses nor is there an option to filter for #ports like :80 & :443 to deal with restrictive #firewalls (i.e. on public #WiFi)…
- there are flags like
ipv6=yesbut neitheripv4=yesnoripv6=noyielded me other resultd than #IPv6webtunnelbridges…
And before anyone asks: Yes, I do have a "legitimate purpose" as some of my contacts do need Bridges to get beyond a mandatory firewall and/or do use #TorBrowser (through an #SSH tunnel) to circumvent Tor & #VPN blocks and maintain privacy (as many companies do block sometimes entire #Hosters' ASNs due to rampant #scrapers…
@tails_live @tails @torproject plus support for meek, snowflake, webtunnel and non-#obfs4 #Bridges seems missing in #Tails.
- It would also help if #BridgeDB allowed to actually select #IPv4 and not just #IPv6 and select ports (i.e. 80 & 443) on top of that.
Cuz to this day I've to yet see an IPv4-#webtunnel #bridge…
🐦🔥nemo™🐦⬛ 🇺🇦The Tor Project celebrates a major victory against online censorship, deploying its 300th WebTunnel bridge! 🎉 This milestone expands internet access in censored regions by disguising Tor traffic as regular web activity. Learn how this helps bypass restrictions: [https://cyberinsider.com/tor-celebrates-300th-webtunnel-bridge-milestone-in-fight-against-censorship/] #TorProject #WebTunnel #Censorship #InternetFreedom 🛡️🌐 #newz
Right now the problem with @torproject #BridgeDB is that I can't get #webtunnel bridges on #IPv4 even when I try to specify those by setting ipv6=no at the URL:
https://bridges.torproject.org/bridges?transport=webtunnel&ipv6=no
And no, removing IPv6 from the URL doesn't yield any IPv4 results either.
https://bridges.torproject.org/bridges?transport=webtunnel
It would be better if #BridgeDB would have a radio button / switch to choose IPv4 & #IPv6 for this reason.
#WhatsMissing: A tool to check if #TorBridges are still available/online/reachable that one can use either #standalone (with #TorBrowser and/or #Tor Expert Bundle) or on @tails_live / @tails / #Tails.
- Cuz I do run into issues and kinda want to sort #Bridges by availability so I don't waste time on a #TorBridge that is down and also thin-out the list of bridges that ain't online anymore.
Whilst I do acknowledge that @torproject do disrecommend having a huge list of Tor Bridges on hand, I do regularly need them for contacts who are behind a #GreatFirewall and can't #SSH-Tunnel out of it.
- Sadly #BridgeDB doesn't offer good #filtering options so one can't just query types effectively like "I need #webtunnel on #IPv4" or "I can only use Ports 80 & 443 on #IPv6" which may work.
Espechally being able to filter for #IPv4only and not just #IPv6only is something I miss, alongside the filter for #PluggableTransports type as @guardianproject #Orbot seems to only handle #obfs4 and not webtunnel or #meek at all...
- I'm pretty certain that merely pinging a bridge at it's port isn't working as a shure-fire way to check for it's availability.
