#2578 Check the usage of ldb_msg_find_attr_as_uint64
Opened 4 years ago by jhrozek. Modified 2 years ago

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)

2 years ago

Login to comment on this ticket.

Metadata