Hi Timo, hi all, I have worked on a security upload of sssd to get sssd back into testing. As a result, I have uploaded sssd 2.13.1-1 to DELAYED/7 queue just now targetting unstable, addressing the following CVE issues: https://security-tracker.debian.org/tracker/CVE-2026-6245 https://security-tracker.debian.org/tracker/CVE-2026-12610 https://security-tracker.debian.org/tracker/CVE-2026-14474 https://security-tracker.debian.org/tracker/CVE-2026-14476 I plan to push my changes to a Git repo under my personal account on salsa (as I lack permissions for the sssd-team group): https://salsa.debian.org/sunweaver/sssd (including the release tag debian/2.13.1-1). However, salsa is currently having issues with forking the original sssd-team/sssd repo into my personal name space. So, I will try to push the changes later. Also, as a member of the Debian Edu team (consuming sssd already now, but even more for the Debian Edu 14 release), I'd like to become co-maintainer of sssd in Debian. Thanks! Cheers, Mike
Thanks for working on sssd! Mike Gabriel <sunweaver@debian.org> writes: Salsa invite for 'sunweaver' to become Maintainer of the sssd-team on Salsa. Unless someone objects, I suggest that you push to the real sssd git project instead of your fork. There seems to be nobody else actively working on it anyway. Further: The sssd-team is small, just sssd, ding-libs and the *-wrapper projects: https://salsa.debian.org/sssd-team My focus in the team has been on *-wrapper, and I don't recall anyone else lately contributing to any of these projects. What do you think about moving all of these projects into the /debian/ Salsa namespace? We could also change the Maintainer field to some group with more participators, such as the pkg-security or Debian Commons teams. Both changes may bring more new contributors, as more people will be able to commit improvements and/or feel entitled to work on sssd-related projects. /Simon