You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for a great exporter.
I see that the only reason this app is split in two subcomponents is to avoid running the whole thing as root. It seems that the only place that actually need root is running smartctl subprocess.
Dont you think exporter can be dramatically simplified if there is option to skip smart_exporter_helper and run sudo smartctl directly instead. sudo is flexible enough to allow only smartctl for designated user.
The text was updated successfully, but these errors were encountered:
@altmind Yes, sudo is flexible enough. It is a trade-off between system configuration (which we cannot really manage) and dependencies (which we have control over).
In addition, this separation allows to put many more restrictions into place. Think about ProtectSystem=full, PrivateDevices (via systemd) etc. etc. all of which wouldn’t be possible if smartctl needs to run as a child of the web server process.
Thanks for a great exporter.
I see that the only reason this app is split in two subcomponents is to avoid running the whole thing as root. It seems that the only place that actually need root is running smartctl subprocess.
Dont you think exporter can be dramatically simplified if there is option to skip
smart_exporter_helper
and runsudo smartctl
directly instead. sudo is flexible enough to allow only smartctl for designated user.The text was updated successfully, but these errors were encountered: