Learn more about these different git repos.
Other Git URLs
The logic of the SELinux processing is split between the provider and the responder. This has caused headaches especially with getting offline processing right.
The provider also writes a "score" into the database and the responder acts upon the score. That's not correct architecture-wise, the provider should be just providing data, not providing much processing logic.
We should move the processing logic to the responder and only update the database in the provider.
Internal change only. No RHEL clone.
rhbz: => 0
milestone: NEEDS_TRIAGE => SSSD 1.10 beta
owner: somebody => mzidek
patch: 0 => 1
review: => 0
resolution: => fixed
status: new => closed
Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.10 beta
SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here:
If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.
Thank you for understanding. We apologize for all inconvenience.
to comment on this ticket.