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

Stop requiring the latest git commit in advisory-db to be signed #629

Closed
Shnatsel opened this issue Aug 4, 2022 · 1 comment · Fixed by #816
Closed

Stop requiring the latest git commit in advisory-db to be signed #629

Shnatsel opened this issue Aug 4, 2022 · 1 comment · Fixed by #816
Labels
good first issue Good for newcomers

Comments

@Shnatsel
Copy link
Member

Shnatsel commented Aug 4, 2022

We currently require the presence of some signature on the latest commit in advisory-db repo for cargo audit and other tooling that uses rustsec crate to work.

This is completely useless in that it doesn't add any security. And it has broken production users twice now (both times for just a few minutes before it was noticed and fixed, but still).

We should disable that check.

@sidunder
Copy link
Contributor

I'll have a go at creating a PR for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants