Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Patch dhvirtualenv for setuptools DO NOT MERGE #5473

Closed
wants to merge 3 commits into from

Conversation

kushaldas
Copy link
Contributor

Status

Dummy PR

Description of Changes

Fixes #.

Changes proposed in this pull request:

Testing

How should the reviewer test this PR?
Write out any special testing steps here.

Deployment

Any special considerations for deployment? Consider both:

  1. Upgrading existing production instances.
  2. New installs.

Checklist

If you made changes to the server application code:

  • Linting (make lint) and tests (make test) pass in the development container

If you made changes to securedrop-admin:

  • Linting and tests (make -C admin test) pass in the admin development container

If you made changes to the system configuration:

If you made non-trivial code changes:

  • I have written a test plan and validated it for this PR

If you made changes to documentation:

  • Doc linting (make docs-lint) passed locally

If you added or updated a code dependency:

Choose one of the following:

  • I have performed a diff review and pasted the contents to the packaging wiki
  • I would like someone else to do the diff review

Mozilla's keyserver went down, and they might just leave it that
way. Their release signing key is available on another one, but that
doesn't seem to be the result of any official policy I can find. The
closest thing to guidance comes from a blog post instructing us to
obtain the key from the archive server along with the
software[1]. This changes the Dockerfile to do that.

Recent versions of geckodriver are being signed with the release key,
so we'll now use it to verify that package too.

We were also using an expired version of the Tor release signing key,
kept in our repo, so I'm following their instructions[2] for obtaining
the key instead.

Finally, this updates all three packages.

[1] https://blog.mozilla.org/security/2019/06/13/updated-firefox-gpg-key/
[2] https://support.torproject.org/tbb/how-to-verify-signature/
@kushaldas kushaldas force-pushed the patch_dhvirtualenv_for_setuptools branch from 5f496f8 to 71291e9 Compare September 1, 2020 13:13
This patched deployment.py file for dh-virtualenv installs
known working setuptools==46.0.0 in the virtualenv, and then
it will try to install dependencies for SecureDrop.

Fixes #5471
@kushaldas kushaldas force-pushed the patch_dhvirtualenv_for_setuptools branch from 71291e9 to 039861a Compare September 1, 2020 13:35
Comment on lines +147 to +153
self.pip_prefix2 = [
os.path.abspath(os.path.join(self.bin_dir, 'python')),
os.path.abspath(os.path.join(self.bin_dir, 'pip')),
"install", "--no-cache-dir", "--require-hashes", "-r",
"/tmp/setup-requirements.txt"] # nosec

subprocess.check_call(self.pip_prefix2)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the modified code from the deplopment.py in the container.

@conorsch
Copy link
Contributor

conorsch commented Sep 2, 2020

Superseded by #5472

@conorsch conorsch closed this Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants