-
Notifications
You must be signed in to change notification settings - Fork 270
spec: change passkey_child owner #7431
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
Conversation
|
ACK, thanks. |
|
Actually... it's unclear if group should be '%{sssd_user}' Currently the logic is following:
The idea is to restrict UIDs able to run privileged binaries. Since 'passkey_child' isn't privileged, following this logic it should be 'root:root' Another note: if we stick to root:sssd, then Makefile.am :: install-exec-hook also should be updated: |
|
mmm I don't have a strong position in any sense. @sumit-bose WDYT? |
|
Hi, I think it would make sense to follow Alexey's "non-privileged binaries" reasoning and use About "executable by anyone", since users should be able to register their keys with the HTH bye, |
Ah, indeed, thank you. @ikerexxe , then please make it root:root, as 'p11_child'. |
passkey_child owner was incorrectly set to $sssd_user:$sssd_user, when it should be root:root. Correcting it. Fixes: 30daa0c ("spec: update to include passkey") Signed-off-by: Iker Pedrosa <ipedrosa@redhat.com>
passkey_child owner was incorrectly set to $sssd_user:$sssd_user, when it should be root:$sssd_user. Correcting it.
Fixes: 30daa0c ("spec: update to include passkey")