Hi, Please don't use pastebins for the test plan, but rather add the instructions directly to the bug. Pastebins usually have an expiration date, and it's better to keep everything on the record in case of regression.
The test plan should be a series of steps that anyone could reproduce, with enough information as to the expected result. I believe the contents of the test plans would fit this definition, except for the part with the configuration files: you should explain which changes should be done, rather than just dumping the final file and expect the verifier to figure out what changed. This is useful not just for the verifier but also for us to understand what your test plan actually entails. The section [Where problems could occur] REALLY needs to be addressed. It's important because it oftentimes leads to changing the test plan to account for those potential issues, which might in turn change the contents of your patch. Please leave a comment once it's done, our sponsorship dashboard doesn't take edits into account when checking if there was recent activity :) And of course we'd really love an ACK from the Security folks on the latest version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2109673 Title: Authentication with smartcard is not working with apparmor DENIED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2109673/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
