-
Notifications
You must be signed in to change notification settings - Fork 165
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
remove URL fetch of keys/artifacts server-side #735
Conversation
Signed-off-by: Bob Callaway <bob.callaway@gmail.com>
When and how do you want to roll this out? |
It depends on how many releases we have before we go 1.0; given that it does deprecate function, it would be good to announce it in the next release (perhaps just the sharding stuff) and then we have a follow-on release that addresses the API (i.e. move to gRPC) and this fix. Thoughts? |
SGTM, so hold this until we cut the next release? |
yup, sounds like a plan. @cpanato we should include a note in the next rekor release noting that the "server side remote fetching of resources will be removed in the next release" (feel free to re-word) |
https://github.com/sigstore/rekor/blob/12d1a47c7ac986932a2734cb855c642ac01ffde4/pkg/api/index.go also has another instance of this pattern we should remove. |
Did we want to include something in 0.6 around the deprecation of this? |
it was in the changelog
…On Wed, Apr 13, 2022 at 5:35 PM Hayden B ***@***.***> wrote:
Did we want to include something in 0.6 around the deprecation of this?
@cpanato <https://github.com/cpanato> fyi
—
Reply to this email directly, view it on GitHub
<#735 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVWTJLZXIUOVHCV6CPH4RDVE44ZNANCNFSM5QY6XA3A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Ah missed it, all good! |
Should be safe to merge after that goes out! |
We originally added the ability for Rekor API callers to specify URLs to fetch public keys, artifacts, & signatures to simplify fetching larger objects rather than forcing clients to download them locally and upload them to Rekor for verification.
Now that we have the
hashedRekord
type, this patch removes the ability for the Rekor server to fetch arbitrary URLs before making entries into the log, largely due to the risk of SSRF.Note that the option for
rekor-cli
to specify URLs on the command line remains, as the CLI tool will download the artifacts locally and then insert the relevant contents in the appropriate position within the payload submitted to the Rekor server.Signed-off-by: Bob Callaway bob.callaway@gmail.com