Deploy our TBB update archives on a secure machine
We need a secure hosting of our .mar update archives for the TBBs. One way to make it more secure is pinning attributes of the TLS certificate in Tor Browser itself. There are probably others that should be investigated.
Activity
Some of the existing Firefox prefs that we can use are:
app.update.cert.requireBuiltIn app.update.cert.checkAttributes app.update.certs.1.issuerName app.update.certs.1.commonName
We should be able to add as many attributes as we want under app.update.certs.1. (but brade and I have only tested with issuerName and commonName which are the ones that Mozilla uses).
See: prefs: http://mxr.mozilla.org/mozilla-esr24/source/browser/app/profile/firefox.js#92
update manifest onLoad handler: http://mxr.mozilla.org/mozilla-esr24/source/toolkit/mozapps/update/nsUpdateService.js#3370
checkCert from CertUtils.jsm: http://mxr.mozilla.org/mozilla-esr24/source/toolkit/modules/CertUtils.jsm#119
gk -- Do you think these existing mechanisms provide enough flexibility for TBB? (brade and I think they do)
Replying to mcs:
gk -- Do you think these existing mechanisms provide enough flexibility for TBB? (brade and I think they do)
Yes, I think so, too. Although we need to be careful when pinning the cert(s) attribute(s) to not lock users in case our cert(s) need to get replaced by (a) newer one(s)...
