Opened 2 years ago

Closed 12 months ago

#22925 closed enhancement (wontfix)

Make the extension whitelist public key cryptography based.

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

Description

If/when the Tor Browser people decide to do the sensible thing and start signing all of the XPIs bundled with Tor Browser, the extension whitelist can be made more resilient to Tor Browser changes by validating XPI signatures with it's own copies of the public key.

Till then it will be somewhat fragile, though new extensions don't get added very often, so it's "merely" a matter of keeping in sync with the browser.

Child Tickets

Change History (4)

comment:1 Changed 2 years ago by yawning

The XPI signing method is broken (#22971), so I need to think of something better.

comment:2 Changed 2 years ago by yawning

This *might* be vaguely ok if it used hardened SHA1. In that case, there's a PKCS7 library at https://github.com/fullsailor/pkcs7 that purports to support what is required.

But this ultimately depends on NoScript, torbutton and torlauncher being signed with non-Mozilla keys.

comment:3 Changed 2 years ago by yawning

#22974 is the bug for "sign NoScript with different signing keys".

comment:4 Changed 12 months ago by yawning

Resolution: wontfix
Status: newclosed

This project is deprecated, and none of these will ever be fixed.

Note: See TracTickets for help on using tickets.