Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Add dummy release process to test.sh #457

Closed

Description

@diracdeltas

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.

Activity

  1. diracdeltas commented on Aug 20, 2014

    @diracdeltas
    ContributorAuthor

    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.

  2. zoracon commented on Feb 13, 2019

    @zoracon
    Contributor

    Closing due to new changes since this conversation took place, but will still be linked to referenced newer issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions