Custom Query (69 matches)


Show under each result:

Results (31 - 45 of 69)

1 2 3 4 5
Ticket Summary Owner Component Milestone
#24231 users looking for Tor Browser uninstall instructions should find the correct ones traumschule Webpages/Website website redesign

It's too easy for users who are trying to uninstall Tor Browser on macOS to find and try to follow its instructions (which won't usually work). The FAQ text at that links to it also could use improvement. There might be similar ambiguous/misleading instructions elsewhere; I haven't exhaustively checked.

#24255 Download page offers "source" for Tor, but everything else on that page is Tor Browser Webpages/Website website redesign

Our download page offers Tor Browser for various platforms, and also a "source" option. But the source option only gives you a Tor tarball, and that's not the source for the binaries on that page.

Maybe we should have a web page for the little-t-tor component, with pointers to things including source tarballs.

And then change the download page to give you pointers on how to reconstruct the tor browsers that it offers (which is actually quite hard, but that's another matter).

#24376 Search backend for websites - Test and deploy Solr hiro Webpages/Website website redesign
#24727 Add onion service for and use it Webpages/Website

Currently don't have onion. Use .onion to determine whether user is via Tor or not.

#25131 Add a security.txt file to Webpages/Website website redesign

security.txt files give people the information they need to contact Tor when they find a security issue.

It's an IETF draft, and Google has done it, so maybe we should too:

We can use the existing information at:

And we might want to:

  • add a PGP key file
  • add a signature
  • maybe add a policy or acknowledgements when we decide how they work
#25218 Update screenshots to use obfs4 bridges (instead of obfs3) traumschule Webpages/Website website redesign

...then choose the transport type you want to use. obfs3 is currently the recommend type...

#25475 TB Credits traumschule Webpages/Website website redesign

We should have a page of contributors, either on the website or Tor browser. Tor Community members, translators etc

#25640 coding hiro Webpages/Website website redesign

ticket to track the coding work for new site

#25641 content for isabela Webpages/Website website redesign

This ticket is to track the work to create content and review content related to the new site

#25642 translation of emmapeel Webpages/Website website redesign

this ticket is to track the work to send string to be translated and translation progress of it.

#26133 Add OnionBrowser to redesigned page traumschule Webpages/Website website redesign

Many IOS users have a hard time finding an "IOS Torbrowser" that TorProject recommends, this can be seen by the many questions that are asked on TorProject's twitter on how to download TorBrowser for IOS. It would be great if A link is added to the redesigned TorProject download page that directs users to Mike Tigas's OnionBrowser. This would also reduce the number of IOS users that accidentally download a NON-recommended "IOS Torbrowser" like "Red Browser".

A disclaimer could be added under the link to the OnionBrowser app saying, "This app is recommend by TorProject but it is not directly developed by TorProject nor directly funded by TorProject".

#26307 Add link to Tor SlackBuild on download-unix.html.en Webpages/Website website redesign

I thought it would be nice to add link to the Tor SlackBuild on download-unix.html.en. The SlackBuild works fine and is updated regularly.

The code would be something like this:

<tr class="beige">
<td align="center"><img src="$(IMGROOT)/distros/slackware.png" alt="Slackware"></td>
<td colspan="2"><a href=""></a></td>
<a href="<page docs/tor-doc-unix>">Linux/BSD/Unix</a><br>

If nobody wants to design a new logo, there's generic.png in /images/distros/ folder

#26314 Create "Learn More" Landing Page for TBA Webpages/Website

When TBA is first launched there is a "Learn More" link the user can click. We should take advantage of this and create a useful webpage where the user can learn more. (Orfox currently has this, too, and the link goes to the Guardian Project's Orfox page.

#26539 add checksums to download page; make checksum vs. sig file purpose much clearer traumschule Webpages/Website

Gpg recently failed to verify a Tor Browser download - a first for me. Since data errors in downloads aren't as common as years ago, I assumed an error in the *.asc sig file itself, or other issues.

Such as my Linux GPG version not playing well with the version used to sign Tor Browser.

I wanted to verify checksum of the downloaded TBB, but after a few searches on TorProject didn't find the checksum, I re-download TBB. It was faster in the long run, but it's a big package to re-download for users with limited data plans, when a few byte checksum would suffice to see if there was a download data error.

I propose that checksum files - or a prominent link, be added to the download page - not make users hunt them. That's how many well run projects seem to do it - app packages, sig files & checksums are all easily found, or have links on the same page.

The statement, "See our instructions on how to verify package signatures, which allows you to make sure you've downloaded the file we intended you to get. Also, note that the Firefox ESR in our bundles is modified from the default Firefox ESR " should be placed above the packages & sig files, where users are far more likely to see it.

The wording could be stronger, clearer - why users would want to verify the TBB / other packages PGP signatures of downloads, EVEN from TorProject's site (not rely solely on checksums). A brief statement why verifying signed packages is important & how it's unrelated to using checksums. If users (of anything) don't understand a real purpose or need, they're more likely to skip steps.

I could write something to make changes, additions & submit for consideration, but only if there's interest in making changes to general security methods to educate users, that work for many products.

  • Verification instructions: They're generally good & someone did a lot of work, but many users unfamiliar w/ PGP / GPG's real purpose & the procedures may be clueless.

On the Windows verify instructions (maybe Linux, OS X), it's unclear which signature & which "package" they're verifying. If they're installing GPG or gpg4win, the instructions should include steps (or link to clear instructions) to first verify GPG itself (once), then a separate verification of downloaded Tor products - EVEN from TorProject's https site.

The statement, "make sure you've downloaded the file we intended you to get." means little to non-gpg users or slightly familiar. To many, they downloaded the correct platform package, therefore they "have the file intended for their OS." As far as they know, they did everything required.

#26774 I'd like to link to the download page, with an anchor in the "source code" tab Webpages/Website

When I do release announcements, I say "you can find the source code in the usual place". I'd really like to link to the download page instead -- but the download page is pretty big, and people are likely to get confused. Instead, I should link to the "source code" header in particular... but I don't see a way to do that in our current download page.

Any solution or alternative would be welcome.

1 2 3 4 5
Note: See TracQuery for help on using queries.