Opened 3 years ago

Closed 3 years ago

#21319 closed defect (duplicate)

Update verification fails, but update still applies

Reported by: Digitalcourage Owned by: yawning
Priority: Medium Milestone:
Component: Archived/Tor Browser Sandbox Version:
Severity: Minor Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

This resembles an issue Tor Messenger had (#19809), but I downloaded https://www.torproject.org/dist/torbrowser/7.0a1/sandbox-0.0.3-linux64.zip manually and started it.

Everything works, but these error messages on the console worry me:

2017/01/25 18:MM:SS update: Downloading https://cdn.torproject.org/aus1/torbrowser/7.0a1-hardened/tor-browser-linux64-6.5a6-hardened-7.0a1-hardened_ALL.incremental.mar
2017/01/25 18:MM:SS update: Validating Tor Browser Update.
2017/01/25 18:MM:SS update: Shutting down old tor.
2017/01/25 18:MM:SS tor: Jan 25 18:MM:SS.000 [notice] Catching signal TERM, exiting cleanly.
2017/01/25 18:MM:SS tor: ==3==AddressSanitizer CHECK failed: ../../.././libsanitizer/sanitizer_common/sanitizer_stoptheworld_linux_libcdep.cc:326 "((sigprocmask_status)) == ((0))" (0xffffffffffffffda, 0x0)
2017/01/25 18:MM:SS tor: SRAT init
2017/01/25 18:MM:SS tor: SRAT warning: cannot find Memory Layout File. Stack trace will be probably wrong.
2017/01/25 18:MM:SS update: Updating Tor Browser.

2017/01/25 18:MM:SS update: ERROR: Error verifying signature.
2017/01/25 18:MM:SS update: ERROR: Not all signatures were verified.

Child Tickets

Change History (1)

comment:1 Changed 3 years ago by gk

Keywords: sandboxed 0.0.3 binary removed
Resolution: duplicate
Status: newclosed

It just says so. In fact it is checking the signature. But it is done with the backup key (we are about to phase out our regular MAR signing key and rotate). This is a duplicate of #15532.

Note: See TracTickets for help on using tickets.