Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T17:22:01Zhttps://gitlab.torproject.org/legacy/trac/-/issues/11289FAQ entry for where Tor's data directory is2020-06-13T17:22:01ZDamian JohnsonFAQ entry for where Tor's data directory isI just took a peek in our faqs to see if there was a "Where is my data directory?" entry I could link to. We don't seem to have one, and [tor's man page](https://www.torproject.org/docs/tor-manual.html.en) says "Store working data in DIR...I just took a peek in our faqs to see if there was a "Where is my data directory?" entry I could link to. We don't seem to have one, and [tor's man page](https://www.torproject.org/docs/tor-manual.html.en) says "Store working data in DIR (Default: @LOCALSTATEDIR@/lib/tor)". I have no clue what that macro expands to, nor would I expect users to. :)
If we can't clarify the manual page then this seems like something we should include in our FAQ since it in turn defines the path of our authentication cookie among other things.WebsiteV3Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/10990Shrink the FAQ2020-06-13T17:21:52ZMatt PaganShrink the FAQThe wiki FAQ entries have been transferred to the main website FAQ. Now the page needs to be improved.
* Add all subheads to the top of the FAQ for easier navigation.
* Delete entries that are outdated, no longer relevant, or not frequ...The wiki FAQ entries have been transferred to the main website FAQ. Now the page needs to be improved.
* Add all subheads to the top of the FAQ for easier navigation.
* Delete entries that are outdated, no longer relevant, or not frequently asked on the help desk.
* Consolidate Tor Browser and Tor Browser 3 subsections.
* Move sha256sum verification to the signature verification section.
* Migrate information on setting up a relay to a dedicated page.
* Migrate Abuse questions to the Abuse faq and kill the subsection.
* Dedicated page for Alternate designs we don't do yet.
* Kill Compilation and installation subsection.
* Consolidate questions that duplicate answers.website redesignMatt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/14005cgit makes our gitweb links point to wrong parts of git2020-06-13T17:22:37ZMatt Pagancgit makes our gitweb links point to wrong parts of gitIt's great that we've updated our gitweb to cgit. Lookin' fancy. We should update all the hyperlinks on our website pages to cgit format. After the update to cgit, our links point to all the wrong places.It's great that we've updated our gitweb to cgit. Lookin' fancy. We should update all the hyperlinks on our website pages to cgit format. After the update to cgit, our links point to all the wrong places.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/12865Two installer construction instructions is one too many.2018-10-20T19:40:04ZMatt PaganTwo installer construction instructions is one too many.Tor includes two different NSI files for building the the Tor Expert Bundle installer. One is contrib/win32build/tor.nsi.in, and the other is contrib/win32build/tor-mingw.nsi.in. The former file says right at the top:
; NOTE: This file ...Tor includes two different NSI files for building the the Tor Expert Bundle installer. One is contrib/win32build/tor.nsi.in, and the other is contrib/win32build/tor-mingw.nsi.in. The former file says right at the top:
; NOTE: This file might be obsolete. Look at tor-mingw.nsi.in instead.
Right now tor-mingw.nsi.in is the only file being used to build the actual NSI. I suspect tor.nsi.in is just dead weight.
< armadev> yeah, you should confirm with erinn that nobody has any use for anything in that file, and then remove itMatt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/12577Verifying keys linux documentation2020-06-13T17:22:17ZcypherpunksVerifying keys linux documentationThe linux documentation calls for using the same instructions as OSX. The OSX instructions then use an OSX package name to verify instead of the linux package name. Someone following these instructions on linux will run into an error. ...The linux documentation calls for using the same instructions as OSX. The OSX instructions then use an OSX package name to verify instead of the linux package name. Someone following these instructions on linux will run into an error. It should be noted in the instructions that the linux package name should be substituted for the OSX package name.
Also, the OSX instructions call for a verification that doesn't work on linux (and that contradicts the video instructions): namely, the linux verify command calls for the signature .asc file to be used in conjunction with the .tar package, in that order. The OSX instructions do not require this. The terminal kicks out an "error: file open" error when doing this without the proper command.
Perhaps just adding a couple of simple lines to the linux instructions would be the best solution.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/12575gk should be listed on the signers page2020-06-13T17:22:16ZMatt Pagangk should be listed on the signers pageGeorg signs the distributed Tor Browser packages. Users rely on https://www.torproject.org/docs/signing-keys.html.en as a point of trust when verifying packages. Users need to be informed whose signature is gk's and what his key ID is.Georg signs the distributed Tor Browser packages. Users rely on https://www.torproject.org/docs/signing-keys.html.en as a point of trust when verifying packages. Users need to be informed whose signature is gk's and what his key ID is.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/12467Outdated information on torproject website2020-06-13T17:22:14ZcypherpunksOutdated information on torproject websitehttps://www.torproject.org/projects/torbrowser-details.html appears to contain outdated information.
Additionally, on https://www.torproject.org/projects/torbrowser.html under the section "What is in the Tor Browser?" there is a link po...https://www.torproject.org/projects/torbrowser-details.html appears to contain outdated information.
Additionally, on https://www.torproject.org/projects/torbrowser.html under the section "What is in the Tor Browser?" there is a link pointing to https://www.torproject.org/torbrowser/design/
I think it should actually point to https://www.torproject.org/projects/torbrowser/design/
There are a few other things I have noticed but can't remember. I'm frequently browsing the torproject website so let me know if the report of such minor mistakes is desired.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/12159Windows builds are for 32 and 64 bit systems.2020-06-13T17:22:12ZMatt PaganWindows builds are for 32 and 64 bit systems.The links for Windows packages on https://www.torproject.org/projects/torbrowser.html only say 32-bit. Users are emailing the help desk asking where the 64-bit packages are. But it's the same package. The web page should be clearer.
I ...The links for Windows packages on https://www.torproject.org/projects/torbrowser.html only say 32-bit. Users are emailing the help desk asking where the 64-bit packages are. But it's the same package. The web page should be clearer.
I think the links should say '32/64-bit' where they now say '32-bit'.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/11756Add Korean TBB to download-easy.html2020-06-13T17:22:08ZcypherpunksAdd Korean TBB to download-easy.htmlThe Turkish bundles are not listed on the website:
https://www.torproject.org/projects/torbrowser.html.en
https://www.torproject.org/download/download-easy.html.en
Also, Korean is listed on first link but not on the second one.The Turkish bundles are not listed on the website:
https://www.torproject.org/projects/torbrowser.html.en
https://www.torproject.org/download/download-easy.html.en
Also, Korean is listed on first link but not on the second one.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/11730Please link to the Turkish version of the Tor Browser2020-06-13T17:22:07ZLunarPlease link to the Turkish version of the Tor Browserhttps://www.torproject.org/projects/torbrowser.html should contain a link to the Turkish build.https://www.torproject.org/projects/torbrowser.html should contain a link to the Turkish build.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/11620Inform website visitors about the iOS situation2020-06-13T17:22:06ZMatt PaganInform website visitors about the iOS situationThe FAQ might be the best place to tell users Tor is not available on iOS. If you can think of a better place to say this, please suggest it. We should perhaps mention that the Guardian Project is working on incorporating Onion Browser a...The FAQ might be the best place to tell users Tor is not available on iOS. If you can think of a better place to say this, please suggest it. We should perhaps mention that the Guardian Project is working on incorporating Onion Browser as well.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/11546Project page still has old Torbirdy logo2014-04-27T23:53:30ZMatt PaganProject page still has old Torbirdy logoTorbirdy got a new logo with release 0.1.2 in November 2013. Our project page was never updated to reflect that. The Torbirdy logo on our website does not match the logo on Mozilla's addons page. Where can I find the new Torbirdy logo im...Torbirdy got a new logo with release 0.1.2 in November 2013. Our project page was never updated to reflect that. The Torbirdy logo on our website does not match the logo on Mozilla's addons page. Where can I find the new Torbirdy logo image file?Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/11473PGP key 0xD0220E4B is not listed on the Tor website.2020-06-13T17:22:03ZcypherpunksPGP key 0xD0220E4B is not listed on the Tor website.The signature found at https://www.torproject.org/dist/torbrowser/3.5.4/sha256sums.txt-boklm.asc was created by a key (0xD0220E4B) that is not listed on https://www.torproject.org/docs/signing-keys.html.enThe signature found at https://www.torproject.org/dist/torbrowser/3.5.4/sha256sums.txt-boklm.asc was created by a key (0xD0220E4B) that is not listed on https://www.torproject.org/docs/signing-keys.html.enMatt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/11463Build a new plan for tor-announce and make it happen2018-07-03T22:32:19ZRoger DingledineBuild a new plan for tor-announce and make it happenWe currently use tor-announce only for stable tor releases, and actually since we don't want to announce them until there are TBB packages, lately we've been failing to reliably use it even for that. This is bad for our users.
We should...We currently use tor-announce only for stable tor releases, and actually since we don't want to announce them until there are TBB packages, lately we've been failing to reliably use it even for that. This is bad for our users.
We should figure out what counts as something all our users should learn about, and consistently mail tor-announce when one of those events happens.
(And I should not be the bottleneck for all of these events.)Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/11398Make it clearer that VPNs should not be used for anonymity purposes.2020-06-13T17:22:02ZMatt PaganMake it clearer that VPNs should not be used for anonymity purposes.People often ask the help desk about setting up a VPN with Tor. It should be more clear on our web documentation that they don't actually want this. What I have in mind is merging https://www.torproject.org/docs/faq.html.en#ShouldIUseTor...People often ask the help desk about setting up a VPN with Tor. It should be more clear on our web documentation that they don't actually want this. What I have in mind is merging https://www.torproject.org/docs/faq.html.en#ShouldIUseTorWithAVPN with https://www.torproject.org/docs/faq.html.en#IsTorLikeAVPN and adding a message that Tor or Tor with a bridge is all you need.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/11170Instructions for verifying the sha256sum file belong on the verifying-signatu...2020-06-13T17:21:57ZMatt PaganInstructions for verifying the sha256sum file belong on the verifying-signatures page.Right now we have instructions on verifying the build on our FAQ page (https://www.torproject.org/docs/faq#VerifyDownload), which is not the best format for new documentation. It makes sense to instead provide these instructions alongsid...Right now we have instructions on verifying the build on our FAQ page (https://www.torproject.org/docs/faq#VerifyDownload), which is not the best format for new documentation. It makes sense to instead provide these instructions alongside the rest of our documentation on verifying the integrity of our software with GPG, at https://www.torproject.org/docs/verifying-signatures. Erinn has asked me not to edit the signature verification page directly, so I'm instead attaching a patch of what I had in mind.
If my patch does not reflect the direction we want to take our documentation, we could also think about other ways of getting build verification instructions off the FAQ; for example, creating a dedicated wml page on the deterministic build system.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/10981Write a “how to get support?” section in the Tor Browser User Manual2014-05-05T10:01:57ZLunarWrite a “how to get support?” section in the Tor Browser User ManualThe Tor Browser User Manual must contain a section that will guide users to the support they need. It should point them at the list of known issues, and offer a template on what should be included in an email to the help desk.The Tor Browser User Manual must contain a section that will guide users to the support they need. It should point them at the list of known issues, and offer a template on what should be included in an email to the help desk.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/10891Document setting up a relay for Windows users2020-06-13T17:21:51ZMatt PaganDocument setting up a relay for Windows usershttps://www.torproject.org/docs/tor-doc-relay.html.en provides incomplete information. Windows and Mac users that want to provide a bridge or a relay need to be better informed of their options.
https://www.torproject.org/docs/faq.html...https://www.torproject.org/docs/tor-doc-relay.html.en provides incomplete information. Windows and Mac users that want to provide a bridge or a relay need to be better informed of their options.
https://www.torproject.org/docs/faq.html.en#ConfigureRelayOrBridge could be expanded and moved to this page if it were improved.
Users should know about:
* The Windows expert bundle.
* The Windows Vidalia Bundles.
* The Vidalia standalone package.
* A step-by-step guide on locating and editing the Tor Browser Bundle torrc file.
* Common torrc options such as BandwidthRate (even if it's just a link to the FAQ page).
* The BridgeRelay and ServerTransportPlugin options(?)
* https://trac.torproject.org/projects/tor/wiki/doc/TorBrowserBundle3FAQ#HowdoIconfigureTorasarelayorbridge
* https://trac.torproject.org/projects/tor/wiki/doc/TorBrowserBundle3FAQ#WheredidtheworldmapVidaliagoMatt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/10768Dead link on Tor users page.2020-06-13T17:21:48ZMatt PaganDead link on Tor users page.The Tor users page links to http://www.cbsnews.com/stories/2002/12/03/tech/main531567.shtml from the "They research sensitive topics." bullet point. The story should be about the censorship of Tibetan culture but instead it is an empty b...The Tor users page links to http://www.cbsnews.com/stories/2002/12/03/tech/main531567.shtml from the "They research sensitive topics." bullet point. The story should be about the censorship of Tibetan culture but instead it is an empty blank page.Matt PaganMatt Paganhttps://gitlab.torproject.org/legacy/trac/-/issues/10628Provide better instructions for accessing YouTube.2020-06-13T17:21:45ZMatt PaganProvide better instructions for accessing YouTube.Entering YouTube's HTML5 trial does not appear to make much difference for which videos are accessible and which aren't. Watching the embedded version of videos is a better solution. We should tell people about the latter.Entering YouTube's HTML5 trial does not appear to make much difference for which videos are accessible and which aren't. Watching the embedded version of videos is a better solution. We should tell people about the latter.Matt PaganMatt Pagan