Learn more about these different git repos.
Other Git URLs
On some places, we store UIDNUM to sysdb as uint32_t, sometimes as uint64_t and the same mess is when reading the attributes. In some places we even assign result of function returning uint64_t to variable of uint32_t. This leads to funny endianess bugs.
We need to check the way we handle the IDs and unify the handling in a safe way.
Sumit agreed to check the other occurrences.
milestone: NEEDS_TRIAGE => SSSD 1.13 alpha owner: somebody => sbose
internal only change, no cloning
rhbz: => 0
Not a blocker for Alpha
milestone: SSSD 1.13 alpha => SSSD 1.13 beta sensitive: => 0
Internal-only task and we need to make room for newly arrived tickets.
milestone: SSSD 1.13 beta => SSSD 1.14 beta
Unless someone contributes a fix, this is not in scope of 1.14..
Long-term, it would be awesome to stop using any ldb calls in sssd except the sysdb itself..
milestone: SSSD 1.14 beta => SSSD 1.15 beta
Metadata Update from @jhrozek: - Issue assigned to sbose - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: Canditate to close
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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: - https://github.com/SSSD/sssd/issues/3619
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.