Control: tags -1 wontfix Control: close -1 On Sun, 25 May 2025 10:06:53 +0200 Val Markovic <v...@markovic.io> wrote: > Package: systemd > Version: 257.5-2 > Severity: normal > X-Debbugs-Cc: v...@markovic.io > > Dear Maintainer, > > SetCredentialEncrypted is broken for user services in systemd v257.5. The > detailed bug report has been filed upstream at > https://github.com/systemd/systemd/issues/37598 and has already been fixed in > https://github.com/systemd/systemd/pull/35536 (5 months ago), but it doesn't > seem to be targeting v257 minor releases (for unknown reasons). > > Would it be possible to get the fix for this issue in debian before Trixie is > released? > > I encountered this issue while trying to "kick the tires" of Trixie before the > stable release and it's the only problem I've found (so far) that makes rootless > containers in Podman painful on Trixie. (Podman Quadlets create systemd service > unit files. This is not a bug in Podman, only systemd.) Naturally, this problem > doesn't exist when using rootful containers (since `root` doesn't hit the > premissions issue). > > It would reaaaaally suck to have this bug for the next 2 years and "snatch > defeat from the jaws of victory" for rootless containers on Debian Stable. > Rootless containers are fantastic for improving system security.
Sorry but this is not a bug, it's a new feature that was added recently. Thus, it is not appropriate for manual backporting. You'll have to wait for forky or trixie-backports I'm afraid.
