#498 The proxy back end checks potentially uninitialized variables
Closed: Fixed None Opened 13 years ago by jhrozek.

The functions from proxy_nss_ops structure do not always return the *errnop variable, but our proxy code checks them and uses for determining errors. This can lead to checking random (uninitialized) data:

[sssd[be[proxy]]] [get_initgr_groups_process] (2): proxy -> initgroups_dyn failed (-26406780)[Unknown error 18446744073683144836]

Fields changed

description: The functions from proxy_nss_ops structure do not always return the *errnop variable, but our proxy code checks them and uses for determining errors. This can lead to checking random (uninitialized) data:

{{{
[sssd[be[proxy]]] [get_initgr_groups_process] (2): proxy -> initgroups_dyn failed (-26406780)[Unknown error 18446744073683144836]
}}}
=> The functions from proxy_nss_ops structure do not always return the *errnop variable, but our proxy code checks them and uses for determining errors. This can lead to checking random (uninitialized) data:

{{{
[sssd[be[proxy]]] [get_initgr_groups_process] (2): proxy -> initgroups_dyn failed (-26406780)[Unknown error 18446744073683144836]
}}}

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.3.0
owner: somebody => jhrozek

Fixed in cede23a

fixedin: => 1.3.0
resolution: => fixed
status: new => closed

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.3.0

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

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.

Metadata