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

Retrospective from the recent XZ vuln #412

Open
evelikov opened this issue Apr 7, 2024 · 1 comment
Open

Retrospective from the recent XZ vuln #412

evelikov opened this issue Apr 7, 2024 · 1 comment

Comments

@evelikov
Copy link
Collaborator

evelikov commented Apr 7, 2024

As many of you have seen in the news XZ suffered a very serious vulnerability recently. Looking through the various discussions and reflecting, here are some actions I would love to see:

  • encourage cross reviews from everyone - add to CONTRIBUTING
  • maintenance lack of time vs funds - ditto mention in the CONTRIBUTING/README
  • the fix and test must be in same PR - ditto CONTRIBUTING
  • ban direct pushes to master branch in GH settings - document in MAINTAINERS
  • add protect tags (pattern) in GH settings - MAINTAINERS
  • use signed tags for releases - MAINTAINERS
  • require signed commits for maintainers (how to check/enforce?), recommend for others - CONTRIBUTING
  • list current maintainers (in MAINTAINERS) and general response time (CONTRIBUTING)
  • set security policy (use Github?) and add some docs

@scaronni @xuzhen what do you think?

@scaronni
Copy link
Collaborator

Hi @evelikov I'm fine with all of them. In the meanwhile I've made you an admin, as my time is really limited:

image

Feel free! I would suggest protecting the master branch is an easy win. Thanks!

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

No branches or pull requests

2 participants