Custom Query (101 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (46 - 60 of 101)

1 2 3 4 5 6 7
Ticket Summary Owner Component Milestone
#26314 Create "Learn More" Landing Page for TBA Webpages/Website
Description

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
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.

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

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.

#26781 onion version should link onion addresses Webpages/Website
Description

As per https://onion.torproject.org/ the mapping is www.torproject.org: http://expyuzz4wqqyqhjn.onion/. If http://expyuzz4wqqyqhjn.onion/ is opened as http://www.expyuzz4wqqyqhjn.onion/ it opens a different page. (Screenshots attached).

Also, the links on http://www.expyuzz4wqqyqhjn.onion/ are to cleatnet torproject.org. May be onion version should have onion addresses as links.

#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.

#26837 Move the "research-ideas" tickets to research ideas page Webpages/Website
Description

The Metrics/Analysis trac component has been gathering tickets that are not really suited to being trac tickets. The Metrics team certainly isn't going to look at them any time soon. I had tagged these with the keyword research-ideas.

The ideas page is at https://research.torproject.org/ideas.html on the portal.

#26838 Port the research portal content to Hugo irl Webpages/Website
Description

This will allow easy update to conform to the styleguide and make it easier to edit the content.

#27131 Tor download link links to TBB download page traumschule Webpages/Website
Description

Some pages link to download TBB instead of Tor

Instead they should link to https://www.torproject.org/download/download-unix.html.en

#27293 Expired core people's gpg keys Webpages/Website
Description

Some key files on tpo / linked keys on the core people page are expired and should be re-uploaded. Following output was created with a script.

#27412 make bug tracker links on getinvolved page accessible without login qbi Webpages/Website
Description

The bug tracker link to Tor on https://www.torproject.org/getinvolved/volunteer.html.en requires a trac account. It is very unlikely that anyone visiting this page for the first time (like after clicking "Get Involved" on about:tor) is logged in.

This longer link gives the same result without login.

I don't know though if this should be fixed in trac or the website.

#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

#27423 Sign security.txt Webpages/Website website redesign
Description

From comment:6:ticket:25131:

I suggest we use the tor-security list key, or some other key that many people trust.

#27458 security.txt: Add acknowledgments page to honour our security researches Webpages/Website website redesign
Description

The page will be linked in https://torproject.org/.well-known/security.txt

Details: ​https://tools.ietf.org/html/draft-foudil-securitytxt-04#section-3.4.1 Basically a place to honour the work of former / current security researchers.

This could also go into #25475.

#27540 download: anchors do not work with enabled javascript traumschule Webpages/Website
Description

Go to https://www.torproject.org/download/download.html.en#android https://www.torproject.org/download/download-easy.html.en#android and land in the middle of the warnings.

#27582 add page for Tor controllers Webpages/Website
Description

Maybe under [expert guides], in the FAQ's Advanced Tor usage section, or on the new website

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