<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="generator" content="Windows Mail 17.5.9600.20911"> <style data-externalstyle="true"></style> </head> <body dir="ltr"> <div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"> <div>Hi,</div> <div><br> </div> <div>I’m just asking because of the latest “not-a-bug” [1]. As far as I know, there aren’t many services that need full root access (maybe for getting a low port number). Except for that I don’t see many use cases. Therefore, I think it would be useful to make the decision for root access more explicit, e.g. User=root is needed to start units as root. Also I don’t think it is a sane default is to start any unit as root when there is no valid User property. Even the security of systemd would benefit because it would save people from accidentally running services as root.</div> <div><br> </div> <div>Regards,</div> <div>Mariusz Wojcik</div> <div><br> </div> <div>[1]: <a href="https://github.com/systemd/systemd/issues/6237">https://github.com/systemd/systemd/issues/6237</a><br> </div> </div> </body> </html>