Skip to content
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

The same as #7042 but with "--sssd-user=sssd" and forced 'sssd.conf::user=sssd' by default for 'system' tests #7044

Closed

Conversation

alexey-tikhonov
Copy link
Member

No description provided.

@alexey-tikhonov alexey-tikhonov changed the title The same as #7042 but with "--sssd-user=sssd" The same as #7042 but with "--sssd-user=sssd" and forced 'sssd.conf::user=sssd' by default for 'system' tests Nov 28, 2023
as it doesn't make much sense anyway.
to `sss_cli_make_request_with_checks()`

This requires to make sure 'sss_sssd_*id' are initialized in
`check_server_cred()`
The only intended client of 'sssd_sudo' is 'sudo' that is suid
binary and thus still can access socket.
But if for whatever reason it's undesirable to make 'sudo' use
its CAP_DAC_OVERRIDE capability then socket mode can be changed
to rw-rw-rw -- previous patch will restrict access to the socket
for root only.

The reason for this change is to avoid the need for CAP_CHOWN for
SSSD itself.
from `sss_process_init()` as it's not used anymore
The latter can be zero (example: socket closed during
`sss_cli_recv_rep()`)
@alexey-tikhonov
Copy link
Member Author

tests/test_passkey.py doesn't work when SSSD run under non-root because of the way device is mocked.

@alexey-tikhonov
Copy link
Member Author

centos-8 doesn't have HAVE_PTHREAD_EXT support and isn't expected to run sssd-2.10+ code anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant