Skip to content

ci: fix offline tests on ubuntu-latest#1283

Merged
jku merged 3 commits into
mainfrom
ww/unbrick-ci
Jan 14, 2025
Merged

ci: fix offline tests on ubuntu-latest#1283
jku merged 3 commits into
mainfrom
ww/unbrick-ci

Conversation

@woodruffw

@woodruffw woodruffw commented Jan 13, 2025

Copy link
Copy Markdown
Member

WIP.

This "fixes" the CI by effectively undoing the namespace default changes that Ubuntu made between 22.04 and 24.04. Doing this should have no security impact in practice, since we're already running with full root access on these runners.

The other option here would be to remove unshare entirely, and continue to test the offline tests without actually enforcing their offline-ness. However, I think it's good to keep this around as a backstop, at least for as long as we can 🙂

Signed-off-by: William Woodruff <william@trailofbits.com>
Signed-off-by: William Woodruff <william@trailofbits.com>
Signed-off-by: William Woodruff <william@trailofbits.com>
@woodruffw woodruffw self-assigned this Jan 13, 2025
@woodruffw woodruffw requested a review from jku January 13, 2025 20:26
@woodruffw woodruffw marked this pull request as ready for review January 13, 2025 21:04
@woodruffw woodruffw requested a review from di January 13, 2025 21:04
@woodruffw woodruffw changed the title ci: mess around with unshare ci: fix offline tests on ubuntu-latest Jan 13, 2025

@jku jku left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG (enough) TM

@jku jku merged commit 3963b0f into main Jan 14, 2025
@jku jku deleted the ww/unbrick-ci branch January 14, 2025 07:37
jku pushed a commit to jku/sigstore-python that referenced this pull request Oct 14, 2025
jku pushed a commit to jku/sigstore-python that referenced this pull request Oct 14, 2025
Backport of sigstore#1283

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
jku added a commit that referenced this pull request Oct 24, 2025
* Backport: internal/trust: Fix bug in rekor key lookup

Rekor keyring can (and in future will) have multiple keys:
logs not only get sharded but once rekor-tiles is integrated in the
public good instance, there will be two writable logs for a while.

Backport of #1350

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>

* Backport #1424

Fail less hard when unsupported keys are seen

Current trusted root contains keys this client version does not
understand: the keys are not necessary to verify or sign
bundles with rekor v1

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>

* Backport: ci: fix offline tests on ubuntu-latest

Backport of #1283

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>

* Bump 3.5.x series to 3.5.4

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>

---------

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
Co-authored-by: William Woodruff <william@trailofbits.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants