SSSD / sssd

#3592 Write a regression test for false possitive "corrupted" memory cache
Closed: Fixed Opened by lslebodn.

Closed: Fixed
Reopen Issue

https://pagure.io/SSSD/sssd/issue/3571

  • get user1 to LDAP
  • start sssd
  • query getent passwd -s sss user1 (so we will be sure that user is in memory cache)
  • read seed and hash_size from header of memory cache (they are needed to calculation of hash
  • estimate length of entries stored in mmap cache for user1 (approximately getent passwd -s sss alcik | wc -c) But we can use hardcoded number e.g. 128
  • generate hash for "user1"
  • generate the same hash as in previous step from random ASCII string with length calculated in previous step (RANDOM_STRING)
  • add new user (RANDOM_SRING) into LDAP with random string generated in previous step.
  • query for newly added user getnet passwd -s sss $RANDOM_STRING
  • stop sssd
  • ensure that user1 and $RANDOM_STRING are properly stored in memory cache. (entries will be returned even though sssd is stopped)

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

Metadata Update from @jhrozek:
- Issue priority set to: minor

https://github.com/SSSD/sssd/pull/503

Metadata Update from @lslebodn:
- Issue set to the milestone: SSSD 1.16.2 (was: SSSD 2.0)
- Issue tagged with: PR

Metadata Update from @lslebodn:
- Issue assigned to lslebodn

master:

  • 6dc1de9781ab211a43d24cbaed7969d98abc1cc1
  • fd17e0925dbcafedb878ddf828a37743c115c9dd
  • 8f83feea4586a8fcf4365e0d22e0a16740424cc2
  • 41454a64c714e984423fd6e94ea89d183a73cc67

gcc warning:

  • 1c42c3962577ea4b2d9ed6a8a07179d33756b3b4
Edited by lslebodn

sssd-1-14:

  • 979a474d6ea68449f18b97fa618ac9e9f72be2bd
  • 6c8757680bae643af6d45bfc2d571fae3ba3bad3
  • a1a9988ce782d93665961600779eb9e42e5a9141
  • f42c3a90c03da8d8088cc27586013bf79a094923
  • 1dab4d3abe727cfbffc875a504bfa17a9cb4cb67
  • 9eac3198fc0dc80180f87b2825cfff6f7b0f9d2a

sssd-1-13:

  • 1818a1836e1a0d594d8ed69519923edd7e585c72
  • ed20f00a38783ebdf88d88384c51c02e855450bd
  • 4b37adf6341cc63ed2c860a40962bfa77cb7fed0
  • 7ad10248836943f306bf20ec5a66648edc163196
  • 6c52ae886bd03f78cba9e0985917640b773d7e04
  • 1c424d8a704c01cec3f90aed22e41ce88da69881

Metadata Update from @lslebodn:
- Issue close_status updated to: Fixed
- Issue set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.2)
- 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/4615

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.
Metadata

PR

None
None
High
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.