docs(test): broaden chrome-sandbox suid guard comment

Reframe the assert_setuid comment from "guards against the old %post
chmod pattern" to "guards against any regression that strips the suid
bit" — including but not limited to a %post chmod revert.

The assertion itself catches any loss of the setuid bit on
chrome-sandbox, not just the specific %post chmod regression path.
Per review feedback on #595.
This commit is contained in:
JoshuaVlantis
2026-05-11 07:32:12 +02:00
parent 15813ca11f
commit cf085711f2

View File

@@ -43,8 +43,9 @@ assert_executable "$electron_path"
# chrome-sandbox: setuid bit must be set by the rpm spec's %files
# %attr(4755, ...) entry, not by a %post chmod (#539). The check
# guards against regressing the spec to the old %post chmod pattern,
# which leaves chrome-sandbox unsuid'd if the scriptlet is skipped.
# guards against any regression that strips the suid bit — including
# (but not limited to) reverting to a %post chmod, which silently
# no-ops if the scriptlet is skipped (--noscripts, layered images).
chrome_sandbox='/usr/lib/claude-desktop/node_modules/electron/dist/chrome-sandbox'
assert_file_exists "$chrome_sandbox"
assert_setuid "$chrome_sandbox"