Skip to content

Conversation

@Zeitsperre
Copy link
Collaborator

Overview

This PR adds a few security recommendations. The SBOM and provenance adjustment is for testing purposes as the GitHub Workflow doesn't currently push to DockerHub, but once we no longer have Docker autobuild services, we may be using this for production.

Changes:

  • Updated setuptools to address a CWE issue
  • Restricted the allowed connections in PyPI and TestPyPI workflows
  • Added the nodefaults source in conda configurations
  • Specified a nonroot user for running the Docker service

Related Issue / Discussion

Docker Teams Pro subscription is ending in a few weeks. Birdhouse docker images will need to migrate to using the push option in docker/build-push-action very soon.

@Zeitsperre Zeitsperre self-assigned this Sep 2, 2025
@github-actions github-actions bot added the CI Continuous Integration label Sep 2, 2025
Copy link
Collaborator

@tlogan2000 tlogan2000 left a comment

Choose a reason for hiding this comment

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

LGTM assuming you can fix the docker build failure

Copy link
Collaborator

@tlvu tlvu left a comment

Choose a reason for hiding this comment

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

LGTM, please take a look at my comments.

@tlvu
Copy link
Collaborator

tlvu commented Sep 2, 2025

Just to speed up this PR, as long as the github build works, you can merge this PR. If write permission error when added to PAVICS stack, we can fix in a separate PR.

@Zeitsperre Zeitsperre merged commit 7316f59 into main Sep 2, 2025
11 checks passed
@Zeitsperre Zeitsperre deleted the security-fixes branch September 2, 2025 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous Integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants