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.14.2~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/2078473 Title: Discovery of KRB5 ticket fails even if ticket is discoverable 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 Bug description: tracking bug https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078245 [ Impact ] Even if the krb5 ticket is discoverable, the discovery fails (but actually succeeded) So we cannot retrieve the policies or do any action with the controller. [ Test Plan ] This is not something that can be easily reproduced in a real environment, so the best approach to reproduce this issue is: 1. Get adsys codebase before the fix. You can do this by getting the available version in the archive with the command: apt source adsys 2. Run the TestTicketPath test located in internal/ad/krb5_test.go as many times as needed to get the failure. To run the test, open a terminal and, inside the mentioned directory, runs the test X times with the command: go test -run TestTicketPatch -count X 3. The test can fail due to krb5_init_context changing the errno without returning any error. Without the patched version the test will fail after a number of runs. With the patch, it will not fail. [ Where problems could occur ] We now reset errno to 0, because krb5_init_context() can alter it, even if it succeeds. So the discovery always returns success when it succeeds. Worst case would be that discovery failed but errno is set to 0 but this is handled earlier in the code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2078473/+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
