Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Tor Browser
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,317
    • Issues 1,317
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Applications
  • Tor Browser
  • Issues
  • #15864
Closed
Open
Created Apr 30, 2015 by Mike Perry@mikeperryDeveloper

Differentiate between build and release sha256sums.txt

Windows users on our blog and elsewhere are being confused by the fact that the sha256sums for our exes don't match the downloaded files. This problem will probably get worse once we sign the Mac packages..

We might be able to communicate this to them indirectly by providing two sets of sha256sums.txt files: build-sha256sums.txt and release-sha256sums.txt. Or maybe build-sha256sums.txt and sha256sums.txt...

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking