-
Notifications
You must be signed in to change notification settings - Fork 574
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
grype db publication 2024-08-22 01:31:37 +0000 UTC
db checksum does not match
#2076
Comments
Hi @philroche thanks for the report. I'm taking a look now. |
2024-08-22 01:31:37 +0000 UTC
db checksum does not match2024-08-22 01:31:37 +0000 UTC
db checksum does not match
@willmurphyscode Thank you. The latest grype db published today has no checksum issue.
Scans are being performed successfully with this db. |
Hi @philroche thanks for the report for reporting back that it's fixed! I'm glad things are working for you now. Aside: I'm adding |
Thanks for the quick turnaround |
What happened:
The grype db published on
2024-08-22 01:31:37 +0000 UTC
@ https://grype.anchore.io/databases/vulnerability-db_v5_2024-08-22T01:31:37Z_1724300383.tar.gz 's metadata.sjon checksum entry does not match the checksum of the vulnerability.db resulting in errorunable to update vulnerability database: bad db checksum (/tmp/grype-scratch1220908777/vulnerability.db): "sha256:a11915b8368897dd446ad5cbb855414870297841f8bccc3b466c5c5e9ba5539b" vs "sha256:9aba357712f1f68620ccd19349038e59f17a337189a075f9abea884591925f9b"
when trying to import.Using
grype
command directly to scan does not result in an issue but when using the https://pkg.go.dev/github.com/anchore/grype the issue is present.What you expected to happen:
I expect the checksums to match as they have in previous db updates and imports and scan to succeed.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Example from the previous db published on
2024-08-21 01:31:31 +0000 UTC
Environment:
grype version
:cat /etc/os-release
or similar):The text was updated successfully, but these errors were encountered: