List of xbps-triggers that is NOT safe to be run from outside of chroot

[sgn]

In light of #23239,

I look into some xbps-triggers, and I think those triggers aren't safe to be run from outside of chroot:

• if the libc in chroot and libc in host is differs and elf in chroot couldn't be interpreted by host's libc (ld is hard-coded), execve(2) exit with 126, /bin/sh will search next commands in hosts, and use it instead of chroot's executable.
• system-accounts: check if the user

  void-packages/srcpkgs/xbps-triggers/files/system-accounts

  Line 112 in d148c44

  if ! getent passwd ${_uname} >/dev/null; then

  or group

  void-packages/srcpkgs/xbps-triggers/files/system-accounts

  Line 29 in d148c44

  if ! getent group ${_grname} >/dev/null; then

  exists in host (no options to mitigate?), then create user

  void-packages/srcpkgs/xbps-triggers/files/system-accounts

  Line 113 in d148c44

  useradd -c "$descr" -d "$homedir" -s "$shell" ${user_groups} \

  and group

  void-packages/srcpkgs/xbps-triggers/files/system-accounts

  Line 31 in d148c44

  groupadd -r ${_grname} -g ${_gid} >/dev/null 2>&1

  in host (can be mitigated by groupadd -R -P and useradd -R -P, don't know if they're portable). This one is very problematic because base-files uses this triggers
• to be filled.

---

Thought, @void-linux/pkg-committers @ericonr

[ericonr]

How else would we make a /tmp dir appear in the system? chrooting and running xbps-reconfigure even for base-files will still require it. We could:

• have xbps-reconfigure create /tmp if it can't be found (bad)
• include an empty /tmp directory in base-files, somehow (good)

[github-actions]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

[github-actions]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

[github-actions]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

[github-actions]

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.