[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #21238 [Applications/Tor Messenger]: tor-messenger-linux32-0.3.0b2 BAD signature

#21238: tor-messenger-linux32-0.3.0b2 BAD signature
----------------------------------------+----------------------------------
 Reporter:  BobSmith                    |          Owner:
     Type:  defect                      |         Status:  closed
 Priority:  Very High                   |      Milestone:
Component:  Applications/Tor Messenger  |        Version:  Tor: unspecified
 Severity:  Blocker                     |     Resolution:  invalid
 Keywords:                              |  Actual Points:
Parent ID:                              |         Points:
 Reviewer:                              |        Sponsor:
----------------------------------------+----------------------------------
Changes (by arlolra):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 It looks like your problem is in this line,

   gpg --verify sha256sums-signed-build.txt.asc tor-messenger-linux32-0.3
 .0b2_en-US.tar.xz

 that should just be,

   gpg --verify sha256sums-signed-build.txt.asc

 and you'll need to download the corresponding `sha256sums-signed-
 build.txt` file.

 Then you'll want to run,

    shasum -a 256 tor-messenger-linux32-0.3.0b2_en-US.tar.xz

 and verify that sha you get is in that `sha256sums-signed-build.txt` file.

 Hope that helps.

 This procedure is covered here,
 https://trac.torproject.org/projects/tor/wiki/doc/TorMessenger/FAQ#HowtoverifythesignatureofTorMessenger

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21238#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs