I have reuploaded tarball to github release.

Previous tarball will work fine, but it was accidentally overwritten with output from `make distcheck` and therefore sha256sum and armor file won't match. I re-run release script and uploaded correct artifacts.

I'm sorry for the inconvenience.

Pavel

On 1/29/25 12:19, Pavel Březina wrote:
# SSSD 2.10.2

The SSSD team is announcing the release of version 2.10.2 of the
System Security Services Daemon. The tarball can be downloaded from:
      https://github.com/SSSD/sssd/releases/tag/2.10.2

See the full release notes at:
      https://sssd.io/release-notes/sssd-2.10.2.html

RPM packages will be made available for Fedora shortly.

## Feedback

Please provide comments, bugs and other feedback via the sssd-devel
or sssd-users mailing lists:
      https://lists.fedorahosted.org/mailman/listinfo/sssd-devel
      https://lists.fedorahosted.org/mailman/listinfo/sssd-users

# SSSD 2.10.2 Release Notes

## Highlights

This release fixes a number of minor issues in the spec and services files,
affecting mainly rpm-ostree based systems.

### Important fixes

* If the ssh responder is not running, `sss_ssh_knownhosts` will not fail (but
   it will not return the keys).

* A wrong path to a pid file in SSSD logrotate configuration snippet was
   corrected.

* SSSD is now capable of handling multiple services associated with the same
   port.

* `sssd_pam`, being a privileged binary, now clears the environment and
  doesn't allow configuration of the `PR_SET_DUMPABLE` flag as a precaution.

--
_______________________________________________
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/sssd-devel@lists.fedorahosted.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to