Custom Query (71 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (46 - 60 of 71)

1 2 3 4 5
Ticket Summary Owner Component Milestone
#17805 The website should support "stable" and "oldstable" tor releases cypherpunks Webpages/Website WebsiteV3
Description

Right now we have "alpha" and "stable". But sometimes we want to have an extra stable listed as well.

No hurry on this one.

#31342 Tor donor FAQ gives advice that may be illegal sstevenson Webpages/Website
Description

The Tor donor FAQ could be seen to suggest breaking up payments to avoid being identified to IRS/governments/tax authorities. Could this be considered potentially against the law in some jurisdictions as per structuring laws? https://en.wikipedia.org/wiki/Structuring#Definition

Item 23 of https://donate.torproject.org/donor-faq quoted below.

Is the Tor Project required to identify me as a donor to the United States government, or to any other authority?

If you donate $5,000 or more to the Tor Project in a single year, we are required to report the donation amount and your name and address (if we have it) to the IRS, on Schedule B of the Form 990, which is filed annually. However, it's normal for nonprofits to redact individual donor information from the copy of the 990 that's made publicly-available, and that's what we do. We are not required to identify donors to any other organization or authority, and we do not. (Also, if you wanted, you could give us $4,999 in late 2018 and $4,999 in early 2019.)

Emphasis added.

Perhaps the last line in parenthesis could be left unsaid?

#27421 Tor security policy Webpages/Website website redesign
Description

Tor Project currently has not general security policy. We need to work out a security policy that covers all of Tor: See https://trac.torproject.org/projects/tor/ticket/13968#comment:27

#26836 Update and refresh the research portal Webpages/Website
Description

The research portal isn't the prettiest website, nor does it contain the most up to date information. This ticket will act as a central ticket for tasks around updating and refreshing the research portal.

#25218 Update screenshots to use obfs4 bridges (instead of obfs3) traumschule Webpages/Website website redesign
Description

https://www.torproject.org/docs/bridges.html.en#UsingBridges

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

#30838 Update the Debian instructions for experimental-0.4.1 hiro Webpages/Website Tor: unspecified
Description

The 0.4.1 branch is now separate; the 0.3.4 branches are now deprecated.

We should update the website accordingly: https://2019.www.torproject.org/docs/debian.html.en

This change requires the deb.torproject.org change in #30836, and a successful nightly build of experimental-0.4.1.

#17413 Usability of MacOS installation process traumschule Webpages/Website WebsiteV3
Description

Usability of MacOS installation process

Consequence: User is unable to verify package signature

Steps to reproduce:

  1. Download Tor browser
  1. Go to https://www.torproject.org/docs/verifying-signatures.html.en for instructions.
  1. Read the block of text for MacOS and Linux.
  1. Follow the link at the bottom of that section to:

https://www.gnupg.org/documentation/

  1. Struggle with the information on that page.
  1. Try to go to the SourceForge link there for GPG Mac download.

uBlock Origin blockade: uBlock Origin has prevented the following page from loading:http://macgpg.sourceforge.net/

Because of the following filter

sourceforge.net$other

Found in: uBlock filters – Badware risks

  1. Give up.

What should have happened:

Follow the GPGTools link at the top of the Tor page's Mac/Linux instruction block. https://www.torproject.org/docs/verifying-signatures.html.en


Suggested fixes:

  • Divide the MacOS instructions from the Linux instructions.
  • Add numbers to the procedures... something like this, for the MacOS:
  1. Download Tor Browser and save the signature.asc to your Desktop.
  2. Download and install GPGTools.
  3. Open a Terminal window (Terminal is in /Applications/Utilities or find it with search)
  4. Paste the following into the terminal: [... ...]

...adding links appropriately in the procedure

  • Use link colors to help people visually scan through the pages. Take advantage of the human tendency to skim over text and just read the bold, colored stuff:

-Use a color with better contrast against black (the green is wonderful but too dark for good contrast) -Include more keywords in links

  • Related installation issue that probably belongs somewhere else:

Opening the DMG and installing the Tor Browser: The application file shows a file modification date of Dec 31, 1999, so it's difficult to know whether the downloaded one is newer than one I have already. No version number is in the file name. Get Info (cmd-I) (which not every Mac user knows about) does show a version number, and it also shows the file has a creation date of Dec 31, 2000, which is before the mod date. The weird dates might cause version control issues but are also likely to worry people who see them.

#3893 Verifying-signatures needs some work arma Webpages/Website website redesign
Description

https://www.torproject.org/docs/verifying-signatures.html.en is ridiculously complicated and stuffed with tons of irrelevant information.

We should break it into 2 pages. The list of keys that signs sub-components and/or email should be on a completely separate page. The only keys on this page should be those that actually sign user-facing packages: TBB and (maybe) the vidalia expert bundles.

The page should walk the user through verifying a signature of a specific package for each platform. The page should focus on only one key and only one package. This package should probably be TBB.

Also, much of the material on this page is out of date. For example, the Mac utilities are completely different now, are hosted at a new URL, and now have a GUI that handles the key import process (but sadly not package signature verification). They do at least put the gpg binary into the system path, so you no longer have to grovel through /Applications in order to find it.

#23446 Write a guidelines documentation for requirements with Tor integration by third parties tbb-team Webpages/Website website redesign
Description

I heard that one of the discussions in the Montreal meeting was "Encouraging Tor integration by third parties" which spawned for me the idea that there must be some guidelines documentation the requirements that should be met for each use case. For example for browsers (where integrating Tor is a goal with Brave in private browsing and it has been suggested by the (ex?)-CEO of Mozilla) among the requirements I can think of,

  1. Having the user agent the same as the Tor Browser (Otherwise fingerprinting would be easy).
  2. Stream isolation should be enforced, otherwise a single exit can watch all traffic.
  3. First party isolation should be enforced.
  4. ...etc

Of course there's already the Tor Browser design documentation, but it doesn't address this question directly, and more importantly those folks don't want to make an alternative Tor Browser, rather just a "Tor mode" to their private browsing that can enable true privacy by design.

What do you think of such an idea?

Note that this finds its parallel with little-t-tor in another ticket that I couldn't find about alternative implementations of the tor client.

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

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.

#22076 adjust text shown on screen based on size of text traumschule Webpages/Website WebsiteV3
Description

When viewing this web page I find I have to increase the size of text because I have poor vision.

If I use the control-+ to increase the text size, your web page forces me to scroll the window left to right to read lines of text.

Use the method that wikipedia.com uses for displaying the screen.

wikipedia.com adjusts the text to fit within the displayed window by making lines shorter as text size increases and making lines longer as text size increases.

Go to wikipedia.com and view any entry. Then do a control-+ to increase text size and see what it does. Then do a control-- to reduce size of text and see what it does. NOTE: I am using Ubuntu 16.04 - hence my control-+ increases text size and control-- will decrease text size. I don't know what keys are used to do this with other operating systems.

Just an idea from a 71 year old with bad eyes.

#30936 clean up pronoun display in people page Webpages/Website
Description

The people page would look better if we hid parts of the pronoun.is URL in the visible link text, e.g., displaying pronoun.is/they instead of https://pronoun.is/they. The link would still go to the same place, though. (This also matches the conventions of a few other pages I've seen that use pronoun.is URLs.)

Merge request in https://dip.torproject.org/web/tpo/merge_requests/1

#24133 community.torproject.org work pili Webpages/Website website redesign
Description

This is the main ticket for the work related to creating community.torproject.org

  • Main stakeholders of this project:
  • Designer for this project: Antonela
  • Developer for this project: Hiro
  • PM for this project: Isabela

Project phases:

  1. content architecture - map current content related to the portal and organize it
  1. whiteboard draw organization of the content into pages
  1. wireframe these pages
  1. create design for these pages [these include design reviews till we are happy with what we have]
  1. start organizing content for the pages (with the design already done we will be working with that)
  1. update high definition mockups with real content
  1. guerrilla user testing #1
  1. start coding the pages
  1. once content is finished we upload them on transifex for translation to start
  1. Once coding is done we can start QA by language (as translations gets complete)
  1. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]
#24132 dev.torproject.org work isabela Webpages/Website website redesign
Description

This is the main ticket for the work related to creating dev.torproject.org

  • Main stakeholders of this project:
  • Designer for this project: Antonela
  • Developer for this project: Hiro
  • PM for this project: Isabela

Project phases:

  1. content architecture - map current content related to the portal and organize it
  1. whiteboard draw organization of the content into pages
  1. wireframe these pages
  1. create design for these pages [these include design reviews till we are happy with what we have]
  1. start organizing content for the pages (with the design already done we will be working with that)
  1. update high definition mockups with real content
  1. guerrilla user testing #1
  1. start coding the pages
  1. once content is finished we upload them on transifex for translation to start
  1. Once coding is done we can start QA by language (as translations gets complete)
  1. [we could do another user test here too before launch if we want - or we can run one after lunch and continue iteration]
#30709 expyuzz4wqqyqhjn.onion redirects to clearnet: 2019.www.torproject.org hiro Webpages/Website
Description

http://expyuzz4wqqyqhjn.onion/docs/tor-manual.html.en redirects to clearnet: https://2019.www.torproject.org/docs/tor-manual.html.en

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