-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add run_as in keylime.conf and avoid executing as root #423
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems good to me and complementary to #409
@aplanas Could you resolve the conflict? |
@lkatalin, should be done! Do you want me to change the |
Thank you, lgtm! Needs one more rebase and it should be good to go. |
Signed-off-by: Alberto Planas <[email protected]>
If `run_as` parameter is set but the user is missing in the system, keylime will log an ERROR when trying to drop privileges, but continue the execution as the current user (usually `root`). This can be a security issue, as the agent is running "silently" as a privileged user. This commit stop the execution if an error is found when dropping privileges for the agent service, and present an `info!` message with the current user and group. Signed-off-by: Alberto Planas <[email protected]>
@lkatalin Rebased, but I did not found any new conflict. |
Add run_as in keylime.conf
If
run_as
parameter is set but the user is missing in the system,keylime will log an ERROR when trying to drop privileges, but continue
the execution as the current user (usually
root
). This can be asecurity issue, as the agent is running "silently" as a privileged user.
This commit stop the execution if an error is found when dropping
privileges for the agent service, and present an
info!
message withthe current user and group.