Hi,
Could someone send me bridge addresses of old bridge protocols like fte, scramblesuit, flashproxy, obfs2, meek-google, etc.,? I’m making an archive of all bridge protocols and I just want a few addresses as examples. Oh, and one more thing: They shouldn’t belong to active or working bridges, only for bridges that once existed but no longer exist.
replying in public because this is all public data, and can be useful to others:
there are probably PTs I forgot, I got at least one of each transport I was able to recall.
from old pt-bundle:
flashproxy: Bridge flashproxy 0.0.1.0:1
obfs2: Bridge obfs2 83.212.100.216:47870 1F01A7BB60F49FC96E0850A6BAD6D076DFEFAF80
obfs3: Bridge obfs3 83.212.101.2:42782 2ADFE7AA8D272C520D1FBFBF4E413F3A1B26313D
from a ticket
fte: Bridge fte 128.105.214.163:8080 A17A40775FBD2CA1184BF80BFC330A77ECF9D0E9
from an old manpage
scramblesuit: Bridge scramblesuit 192.0.2.42:2032 password=WFVTIHBLAHNBXWSUD6WYTEST42LPIPRT
meek:
random example from godoc : Bridge meek 0.0.2.0:1 url=https://forbidden.example/ front=allowed.example
google: Bridge meek 0.0.2.0:1 url=https://meek-reflect.appspot.com/ front=www.google.com
amazon: Bridge meek 0.0.2.0:2 url=https://d2zfqthxsdq309.cloudfront.net/ front=a0.awsstatic.com
azure: Bridge meek 0.0.2.0:3 url=https://az668014.vo.msecnd.net/ front=officeimg.vo.msecnd.net
meek_lite:
amazon: Bridge meek_lite 0.0.2.0:1 B9E7141C594AF25699E0079C1F0146F409495296 url=https://d2cly7j4zqgua7.cloudfront.net/ ff ront=a0.awsstatic.com
azure: Bridge meek_lite 0.0.2.0:2 97700DFE9F483596DDA6264C4D7DF7641E1E39CE url=https://meek.azureedge.net/ front=ajax.aaspnetcdn.com
these are currently valid bridges, but they aren’t secret (they are default bridges)
obfs4: Bridge obfs4 37.218.245.14:38224 D9A82D2F9C2F65A18407B1D2B764F130847F8B5D cert=bjRaMrr1BRiAW8IE9U5z27fQaYgOhX1UCmOpg2pFpoMvo6ZgQMzLsaTzzQNTlm7hNcb+Sg iat-mode=0
meek: Bridge meek_lite 192.0.2.18:80 BE776A53492E1E044A26F17306E1BC46A55A1625 url=https://meek.azureedge.net/ front=ajax.aspnetcdn.com
snowflake: Bridge snowflake 192.0.2.3:80 2B280B23E1107BB62ABFC40DDCC8824814F80A72 fingerprint=2B280B23E1107BB62ABFC40DDCC8824814F80A72 url=https://snowflake-broker.torproject.net.global.prod.fastly.net/ front=cdn.sstatic.net ice=stun:stun.l.google.com:19302,stun:stun.antisip.com:3478,stun:stun.bluesip.net:3478,stun:stun.dus.net:3478,stun:stun.epygi.com:3478,stun:stun.sonetel.com:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.voys.nl:3478 utls-imitate=hellorandomizedalpn
upcomming transports:
webtunnel: Bridge webtunnel 192.0.2.3:1 url=https://akbwadp9lc5fyyz0cj4d76z643pxgbfh6oyc-167-71-71-157.sslip.io/5m9yq0j4ghkz0fz7qmuw58cvbjon0ebnrsp0
conjure: Bridge conjure 143.110.214.222:80 url=https://registration.refraction.network.global.prod.fastly.net/api front=cdn.sstatic.net
3 Likes
Can I send the list here? Just for archival purposes so that the next generation will know how the bridge addresses that used to be used for older bridges.
There’s a detailed timeline of when default bridges were added in the first half of 2016 and how long it took censors to block them: Time delays in censors’ reactions.
See also Censors’ Delay in Blocking Circumvention Proxies and https://www.bamsoftware.com/proxy-probe/significant_dates.txt from the same experiment.
Until 2017, the default bridges were stored in the file Bundle-Data/PTConfigs/bridge_prefs.js in the tor-browser-bundle repository. You can see the history of that file to track changes. Between 2017 and 2022 the list was in projects/tor-browser/Bundle-Data/PTConfigs/bridge_prefs.js in the tor-browser-build repository (history). After #40436, the list moved from bridge_prefs.js to multiple files under /projects/common.
You can also find some information at the Metrics Timeline by searching for “default bridge”.