-
Notifications
You must be signed in to change notification settings - Fork 547
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
cosign verify-dockerfile
is dangerous
#648
Comments
cc @mlieberman85 who I was telling about this race the other day. |
+1, cc @dekkagaijin I thought we already had a bug to do the in place resolution actually |
we (w/@erkanzileli w/@Dentrax) would love to do that issue if you let us do this @mattmoor @dlorenc |
The behavior is consistent with plain-ol It's becoming more and more apparent that we shouldn't have added image discovery functionality to See also: |
Here's a first step to begin breaking out image discovery from signature creation/verification: #662 |
Fixes sigstore#648 Fixes sigstore#707 Signed-off-by: Furkan <furkan.turkal@trendyol.com> Co-authored-by: Batuhan <batuhan.apaydin@trendyol.com>
Fixes sigstore#648 Fixes sigstore#707 Signed-off-by: Furkan <furkan.turkal@trendyol.com> Co-authored-by: Batuhan <batuhan.apaydin@trendyol.com>
Fixes sigstore#648 Fixes sigstore#707 Signed-off-by: Furkan <furkan.turkal@trendyol.com> Co-authored-by: Batuhan <batuhan.apaydin@trendyol.com>
Fixes sigstore#648 Fixes sigstore#707 Signed-off-by: Furkan <furkan.turkal@trendyol.com> Co-authored-by: Batuhan <batuhan.apaydin@trendyol.com>
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Fixes sigstore#648 Fixes sigstore#707 Signed-off-by: Furkan <furkan.turkal@trendyol.com> Co-authored-by: Batuhan <batuhan.apaydin@trendyol.com>
Fixes sigstore#648 Fixes sigstore#707 Signed-off-by: Furkan <furkan.turkal@trendyol.com> Co-authored-by: Batuhan <batuhan.apaydin@trendyol.com>
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Fixes sigstore#648 Fixes sigstore#707 Signed-off-by: Furkan <furkan.turkal@trendyol.com> Co-authored-by: Batuhan <batuhan.apaydin@trendyol.com>
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Description
Today
cosign verify-dockerfile
is dangerous because it verifies and allowsFROM image:tag
vs.FROM image@sha256:deadbeef
. This is dangerous because even if what's currently tagged on the registry is signed properly, there is a race before theFROM
is evaluated (what if it changes!), or (withdocker build
) it's possible that what is in the local cache(!) is what's actually used, and not what was verified! 😬I would propose the following two changes to eliminate this danger:
cosign verify-dockerfile
to rejectDockerfile
s that don't useFROM <digest>
cosign resolve-dockerfile
that allowsFROM <tag>
, but rewrites theDockerfile
toFROM <verified digest>
.cc @dlorenc
The text was updated successfully, but these errors were encountered: