#1423 Examine all uses of ldap_set_option() for endianness issues
Closed: Invalid None Opened 10 years ago by sgallagh.

Ticket #1422 revealed itself to be a subtle endianness issue. We were assigning the minssf option (which required a ber_len_t value - internally an unsigned long) from a signed integer. The implicit conversion was breaking on 64-bit big-endian systems.

We need to examine all calls to ldap_set_option() for similar potential issues.

Fields changed

keywords: => easyfix
milestone: NEEDS_TRIAGE => SSSD 1.9.0
priority: critical => minor
rhbz: => 0
type: defect => task

Fields changed

owner: somebody => pbrezina
status: new => assigned

I went through the code and we are passing correct types to all ldap_set/get_option() calls.

I agree, I checked the calls as well and all conform to the description in the ldap_set_option man page.

resolution: => worksforme
status: assigned => closed

Metadata Update from @sgallagh:
- Issue assigned to pbrezina
- Issue marked as depending on: #1422
- Issue set to the milestone: SSSD 1.9.0

5 years ago

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/2465

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.

Login to comment on this ticket.