Learn more about these different git repos.
Other Git URLs
This requirement came as a part of security audit of the SSSD. It is important (not only) for the auditors to understand how the processes that the SSSD consists of communicate.
We should create a wiki page that describes:
- the SBUS mechanism and how do we verify the identity of the process (client registration, client IDs etc)
- that there is a difference between the private and public pipes (pam vs. nss)
We should also make sure the corresponding code is well documented so that the auditors can cross-reference the code with the document.
milestone: NEEDS_TRIAGE => SSSD 1.9.1
rhbz: => 0
milestone: SSSD 1.9.1 => SSSD 1.9.2
milestone: SSSD 1.9.2 => SSSD 1.9.3
Not critical for 1.9.3
design_review: => 0
milestone: SSSD 1.9.3 => SSSD 1.9.4
Dropping the investigation/documentation tasks to trivial. These can be deferred if needed.
priority: major => trivial
Moving the docs task to 1.9.5
milestone: SSSD 1.9.4 => SSSD 1.9.5
I started the page here: https://fedorahosted.org/sssd/wiki/DesignDocs/IPC
owner: somebody => jhrozek
status: new => assigned
milestone: SSSD 1.9.5 => SSSD 1.10.0
review: => 0
milestone: SSSD 1.10.0 => SSSD 1.10.1
Moving tickets that didn't make 1.10.1 to the 1.10.2 bucket.
Moving tickets that didn't make 1.10.1 to 1.10.2
milestone: SSSD 1.10.1 => SSSD 1.10.2
The 1.11 tasks took precedence. We're going to finish the document during the 1.11.2 stabilization.
milestone: SSSD 1.10.2 => SSSD 1.11.2
milestone: SSSD 1.11.2 => SSSD 1.12 beta
priority: trivial => blocker
milestone: SSSD 1.12 beta => SSSD 1.12 beta 2
There is a separate page:
and also the info was added to our design document:
resolution: => fixed
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.12 beta 2
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.