Hello Denison, or anyone else affected, Accepted adsys into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/adsys/0.16.3~22.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2091940 Title: [SRU] Release adsys 0.16.3 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Noble: Fix Committed Status in adsys source package in Oracular: Fix Committed Bug description: [Impact] Adsys 0.16.3 introduces dependency bumps, and updates to the privilege policy manager to support the newer Polkit versions (>= 124) and their new syntax for defining system admins. It also adds fixes and improvements for certificate autoenrollment, specifically for multiple domains AD environments (i.e. parent.com and child.parent.com). Those fixes involve the refinement of some LDAP queries that were targeting the wrong domain and allowing the default behavior of getting the templates for a specific certificate authority to be overridden through changes in the cepces configuration file. We also fixed an issue with the parsing of (very) large policies, so we can now support even bigger files. Since the behavior updates mentioned only impact policy managers locked under a Pro subscription, this should not impact interim releases. [Test Plan] - For interim releases: Requirements: - Windows Server VM with Active Directory services (AD DS) configured; 1) Configure DCONF policies in the AD controller; 2) Configure a (very) large GPO (around 400kb); 3) Enroll the Ubuntu machine on the domain; 4) Install adsys 0.16.3; 5) Ensure that a user from the enrolled domain can authenticate and that adsys was able to parse and apply the policies correctly. - For LTS releases: Requirements: - Multiple domains environment (i.e. root.com and child.root.com) - Windows Server VM with Active Directory services (AD DS), on root.com. - Windows Server VM with Active Directory services (AD DS), Active Directory Certificate Services (AD CS) and a CEPCES server configured, on child.root.com. 1) Configure privilege policies in the child AD controller; 2) Enable the certificate autoenrollment policy in the child AD controller; 3) Configure a (very) large GPO (around 400kb); 4) Enroll the Ubuntu machine on the child domain; 5) Install adsys 0.16.3; 6) Ensure that adsys was able to parse all the relevant policies; 7) Ensure that a user from the enrolled domain can authenticate and that the privilege policy was applied correctly; 8) Ensure that the machine is enrolled to the correct certificate authority; [Where problems could occur] Since all of adsys external dependencies are vendored, there is no risk of incompatibility with other packages in the Ubuntu release. Unless an internal bug within one of them affects adsys (this would likely have been spotted in CI), bumping their version should not cause issues. If adsys fails to parse a large policy file, it won't be applied. If the policy was enforced on the domain controller, authentication will be denied. This is already the case in the current archive version, so there's no risk of regression here. The changes focused at the Privilege and Certificate managers are locked under a Pro subscription, so they have no impact on interim releases. As for LTS releases, there are two fail points: If adsys fails to apply the privilege escalation policy and the policy is enforced by the AD controller, then authentication will be prevented for users that require this GPO. If the policy is not enforced, then authentication will proceed as normal and polkit will use the system default values for system administrators. If adsys fails to fetch the certificate authorities or enroll the machine to a certificate template, authentication will still be allowed but the machine won't have access to the certificate benefits. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2091940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
