-
Notifications
You must be signed in to change notification settings - Fork 198
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
daemon/upgrader: Print OSTree signature verification text when pulling OCI #5223
Conversation
So with this, here's the output:
|
There's another big piece of tech debt here which is until just today, ostree-ext was archived and I hadn't been publishing new crates. The idea is we'd switch over to bootc on the client side. But anyways I think in the short term we probably need to cut this repo over to pulling ostree-ext via git from bootc, right? Presumably that's how you tested this, by adding a |
Note this doesn't change the output of rpm-ostree could automatically follow through to the OSTree base commit mentioned in the merge commit's metadata, but then presenting it as if the merge commit was signed seems misleading. Any commit could have metadata saying it's a merge of base commit X. So instead we print the verification at pull time, since we have to trust that the configured OCI remote is valid anyway. |
I mean, we definitely could do this, but we'd have to get the presentation right. But this IMO is good enough until we get to proper OCI signing. |
➡️ #5227 |
Marking draft as this depends on #5227 (mind rebasing?) |
Rebased! |
clang format |
…g OCI If using OSTree remote signature verification for an OCI pull, print the verification text we get from ostree-ext.
If using OSTree remote signature verification for an OCI pull, print the verification text we get from ostree-ext.
Requires: containers/bootc#1028