our disobey.net WebTunnel bridge has been updated to tor v0.4.8.19
and our obfs4 bridge has been updated to tor v0.4.8.19
In some countries, Internet service providers or national firewalls block direct access to the Tor network. Tor Browser includes built-in support for bridges and other circumvention tools, but in censored regions you may still need to select or request a bridge to connect successfully. This page offers country-specific guidance on getting Tor Browser connected when access is censored.
@tobi Was ich empfehle ist nen #SSH-Tunnel als #VPN, #XMPP+#OMEMO oder #OnionShare für #Messaging und #WebCall bzw. #JitsiMeet für #Videocalling & #Telefonie.
Für'n "Lebenszeichen" / Beacon würde ich ntfy.sh nutzen.
Gibt es hier Leute, die sich spezifisch mit der Situation in Russland auskennen und best practice Empfehlungen haben oder vielleicht aktuelle Informationsquellen, auch zur juristischen Lage, kennen? Welche Messenger empfehlt ihr? Kompromisse müssen bestimmt gemacht werden, aber sollten tendenziell keine zu steile Lernkurve erfordern, sodass die Familie sich das gut aneignen und sicher benutzen kann. :BoostOK: #fedihelp #askfedi #ITSecurity #Russland #Solidarität #messenger #Sicherheit #digitaleSouveranität #DigitaleSelbstverteidigung #UnplugPutin #UnplugTrump
our disobey.net WebTunnel bridge has been updated to tor v0.4.8.19
and our obfs4 bridge has been updated to tor v0.4.8.19
@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.
I.e.
bridgetest -v4 obfs4 203.0.113.0:80 …
bridgetest -v6 webtunnel [2001:DB8::1]:443 …
bridgetest -list ./tor.bridges.list.private.tsv
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)…
ipv6=yes but neither ipv4=yes nor ipv6=no yielded me other resultd than #IPv6 webtunnel bridges…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.
Cuz to this day I've to yet see an IPv4-#webtunnel #bridge…
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.