You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
To avoid the issue that we're currently having with signature verification on update.rdf in the 4.0.0 release, it would be nice to do the release signing process with a dummy key in test.sh. This would involve making the release signing scripts public, which we haven't done in the past for opsec reasons (as I understand it).
Relatedly, we should come up with a way to sync changes to the release scripts to the airgap machine.
To avoid making the release signing scripts public, we could just have test.sh call out to a checkout of the (private) https-everywhere-releases repo, but I'm not sure how this would work with Travis.
IMO we should just make the release process public, but @pde probably has thoughts on this.
Activity
diracdeltas commentedon Aug 20, 2014
To avoid making the release signing scripts public, we could just have test.sh call out to a checkout of the (private) https-everywhere-releases repo, but I'm not sure how this would work with Travis.
IMO we should just make the release process public, but @pde probably has thoughts on this.
zoracon commentedon Feb 13, 2019
Closing due to new changes since this conversation took place, but will still be linked to referenced newer issues