Some parts of the code will cause an premature exit of the script if an error happens due to external factors. For example when setting ownerships and/or permissions on the final sudo file:
chmod ($perm, "$file")
or do_log ("ERROR: cannot set permissions on $file [$!/$hostname]")
and exit (1);
chown ($uid, $gid, "$file")
or do_log ("ERROR: cannot set ownerships on $file [$!/$hostname]")
and exit (1);
As a consequence not all sudo fragments may be deployed and this may ultimately leave the system in an unmanaged state (loss of privilege).
It would be better to allow such errors to be ignored via a configuration option.
Some parts of the code will cause an **premature exit** of the script if an error happens due to external factors. For example when setting ownerships and/or permissions on the final sudo file:
```
chmod ($perm, "$file")
or do_log ("ERROR: cannot set permissions on $file [$!/$hostname]")
and exit (1);
chown ($uid, $gid, "$file")
or do_log ("ERROR: cannot set ownerships on $file [$!/$hostname]")
and exit (1);
```
As a consequence not all sudo fragments may be deployed and this may ultimately leave the system in an unmanaged state (loss of privilege).
It would be better to allow such errors to be ignored via a configuration option.
patrick
self-assigned this 2025-04-26 08:46:48 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Some parts of the code will cause an premature exit of the script if an error happens due to external factors. For example when setting ownerships and/or permissions on the final sudo file:
As a consequence not all sudo fragments may be deployed and this may ultimately leave the system in an unmanaged state (loss of privilege).
It would be better to allow such errors to be ignored via a configuration option.
Fixed in
78d2d6aff1by adding theignore_errorsflag