Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:26:25Zhttps://gitlab.torproject.org/legacy/trac/-/issues/25730The Tor website's bridges page has old Tor Browser screenshots2020-06-13T17:26:25ZteorThe Tor website's bridges page has old Tor Browser screenshotsWe should update them:
https://www.torproject.org/docs/bridgesWe should update them:
https://www.torproject.org/docs/bridgesGusGushttps://gitlab.torproject.org/legacy/trac/-/issues/24024Potentially misleading illustrations suggest that Tor doesn't stick to a sing...2020-06-13T17:25:25ZcypherpunksPotentially misleading illustrations suggest that Tor doesn't stick to a single guard node in the overview pagehttps://www.torproject.org/about/overview.html.en
The entry node in the third image is different from the one in the second imagehttps://www.torproject.org/about/overview.html.en
The entry node in the third image is different from the one in the second imagewebsite redesignGusGushttps://gitlab.torproject.org/legacy/trac/-/issues/23001On the website, in the 'bridges' section, update references from 'obfs3' to '...2020-06-13T17:25:01ZTracOn the website, in the 'bridges' section, update references from 'obfs3' to 'obfs4'I noticed that in the 'bridges' section on the website, the recommended default pluggable transport still was obfs3. While elsewhere obfs4 is the recommended PT. I guess it's quite minor, but I'd think people get a bit jittery when they ...I noticed that in the 'bridges' section on the website, the recommended default pluggable transport still was obfs3. While elsewhere obfs4 is the recommended PT. I guess it's quite minor, but I'd think people get a bit jittery when they are presented with slightly off information about what obfuscation technique they should actually be using to protect against inspection of their anonymous connection.
So I made a commit (and branch) to remedy this:
https://github.com/stuij/tor-site/commit/ad38186eceabd733efd67d60485aed9da22e3f99
Pull if you think it's worth the trouble (and I didn't mildly or wholly misunderstood something).
Also, I noticed that the 'pluggable transport page' on trac suffered from the same affliction. I updated it slightly where it matters. There's also a section on composing pluggable transports where obfs3 is used, but I didn't dare touch that bit, as the whole section looks a bit outdated:
https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Combiningpluggabletransports
**Trac**:
**Username**: snoekwebsite redesignTommy CollisonTommy Collisonhttps://gitlab.torproject.org/legacy/trac/-/issues/13665Update the obfsbridge setup instructions on the website2020-06-13T17:22:29ZGeorge KadianakisUpdate the obfsbridge setup instructions on the websitehttps://www.torproject.org/projects/obfsproxy-debian-instructions.html.en#instructions
As sysrqb noted, the official obfsbridge setup instructions are actually obfsproxy setup instructions which only support obfs3. The instructions shou...https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en#instructions
As sysrqb noted, the official obfsbridge setup instructions are actually obfsproxy setup instructions which only support obfs3. The instructions should be updated to also include obfs4 which is the future PT. Then, we should also include instructions for FTE.
Furthermore, the page is missing `ExtORPort auto` from the sample torrc. Should we add it there? If yes, we need to make sure that all those people will have tor-0.2.5.x installed.
I hope this is not a duplicate ticket.website redesigncypherpunkscypherpunks