Public bug reported:
[Impact]
Machine and user scripts are not executed on startup/shutdown/login/logoff.
/run has been recently changed to be noexec on jammy. Ensure that we can
execute the scripts in /run/adsys subdirectories. The scripts mecanism has been
reviewed by the security team, so we can reset them as executable.
[Test case]
* Setup some scripts under AD to be executed, one for machine scripts (on
startup), one for user scripts (on login). Those scripts can create some
temporary files under /tmp for instance.
* Reboot and login on the Ubuntu laptop connected with AD by adsys, with ua
attached
* Check that the scripts were executed by testing that the created file under
/tmp are present.
[Where problems could occur]
This is technically a new .mount systemd unit service which takes the same
mount option than /run, but don’t set noexec. The setup is similar than qemu
.mount unit for instance.
Worst impact could be that the script policy manager can’t run the scripts as
it is already the case today.
** Affects: adsys (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973751
Title:
Machines or Users scripts are not executed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973751/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
