Skip to content

Update github.com/cyphar/filepath-securejoin to v0.6.0 and github.com/opencontainers/runc to v1.3.3#448

Merged
mtrmac merged 4 commits into
podman-container-tools:mainfrom
mtrmac:securejoin
Nov 10, 2025
Merged

Update github.com/cyphar/filepath-securejoin to v0.6.0 and github.com/opencontainers/runc to v1.3.3#448
mtrmac merged 4 commits into
podman-container-tools:mainfrom
mtrmac:securejoin

Conversation

@mtrmac

@mtrmac mtrmac commented Nov 7, 2025

Copy link
Copy Markdown
Contributor

This is a replacement for #432 , also updating the users of removed functions.

Do note the licensing conversation in #432 — and how #446 needs an updated filepath-securejoin (does not matter for container-libs, but needed e.g. in podman-container-tools/podman#27466 ).

Cc: @TomSweeneyRedHat . FYI @mheon

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
@mtrmac mtrmac changed the title Update ithub.com/cyphar/filepath-securejoin to v0.6.0 Update github.com/cyphar/filepath-securejoin to v0.6.0 Nov 7, 2025
@github-actions github-actions Bot added storage Related to "storage" package common Related to "common" package image Related to "image" package labels Nov 7, 2025
podmanbot pushed a commit to podmanbot/buildah that referenced this pull request Nov 7, 2025
@podmanbot

Copy link
Copy Markdown

✅ A new PR has been created in buildah to vendor these changes: podman-container-tools/buildah#6487

@Luap99

Luap99 commented Nov 7, 2025

Copy link
Copy Markdown
Member

Looks like you need to bump runc here at the same time, really annoying that the 0.6.0 update introduces breaking changes which means every users must be updates in the right dependency order first. This will be gigantic PITA if the selinux chnage (podman-container-tools/podman#27466) must be backported.

Looking at it closer I doubt we use the selinux code to write labels in untrusted namespaces so maybe we are good without it.

@mtrmac

mtrmac commented Nov 7, 2025

Copy link
Copy Markdown
Contributor Author

Yes

  • Podman wants github.com/opencontainers/selinux v1.13.0 (not part of this PR)
  • That requires github.com/cyphar/filepath-securejoin v0.6.0
  • That removed API and thus needs an update to github.com/opencontainers/runc v1.3.3

This is necessary to allow the update to
github.com/cyphar/filepath-securejoin v0.6.0 .

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
@mtrmac

mtrmac commented Nov 7, 2025

Copy link
Copy Markdown
Contributor Author

Looking at it closer I doubt we use the selinux code to write labels in untrusted namespaces so maybe we are good without it.

All of this is making me wonder whether there shouldn’t be some way to solve the overmounts within runc, without adding all the /proc complexity and overhead to all other simpler users. But I’m not going to try.

Signed-off-by: Miloslav Trmač <mitr@redhat.com>
@mtrmac mtrmac changed the title Update github.com/cyphar/filepath-securejoin to v0.6.0 Update github.com/cyphar/filepath-securejoin to v0.6.0 and github.com/opencontainers/runc to v1.3.3 Nov 7, 2025
podmanbot pushed a commit to podmanbot/buildah that referenced this pull request Nov 7, 2025

@lsm5 lsm5 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@mheon

mheon commented Nov 7, 2025

Copy link
Copy Markdown
Contributor

LGTM once tests are green

@TomSweeneyRedHat

Copy link
Copy Markdown
Contributor

LGTM
with happy tests

@mtrmac mtrmac merged commit 09de135 into podman-container-tools:main Nov 10, 2025
36 of 37 checks passed
@mtrmac mtrmac deleted the securejoin branch November 10, 2025 13:10
TomSweeneyRedHat added a commit to TomSweeneyRedHat/buildah that referenced this pull request Nov 13, 2025
Testing a storage bump in container-libs,
most notably the securejoin bump it drags in.

Those changes are part of: podman-container-tools/container-libs#448

Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
@0xFelix

0xFelix commented Feb 11, 2026

Copy link
Copy Markdown

Can we backport this to podman-5.8?

@Luap99

Luap99 commented Feb 11, 2026

Copy link
Copy Markdown
Member

Can we backport this to podman-5.8?

What do you need this for? This branch is used for our podman releases and backporting these fixes through all projects is additional work for us.

@0xFelix

0xFelix commented Feb 11, 2026

Copy link
Copy Markdown

It's not as important, nevermind. We can wait for Podman 6 libs. Thanks for looking into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

common Related to "common" package image Related to "image" package storage Related to "storage" package

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants