Merge lp://qastaging/~bladernr/checkbox/ppppcc-add-insecure-policy into lp://qastaging/~checkbox-dev/checkbox/ppa-packaging-plainbox-provider-canonical-certification
Proposed by
Jeff Lane
| Status: | Merged |
|---|---|
| Approved by: | Daniel Manrique |
| Approved revision: | 16 |
| Merged at revision: | 16 |
| Proposed branch: | lp://qastaging/~bladernr/checkbox/ppppcc-add-insecure-policy |
| Merge into: | lp://qastaging/~checkbox-dev/checkbox/ppa-packaging-plainbox-provider-canonical-certification |
| Diff against target: |
25 lines (+5/-0) 2 files modified
debian/changelog (+4/-0) debian/control (+1/-0) |
| To merge this branch: | bzr merge lp://qastaging/~bladernr/checkbox/ppppcc-add-insecure-policy |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Daniel Manrique (community) | Approve | ||
|
Review via email:
|
|||
Description of the change
If sudo prompts are going to happen every time a test needs root access, we're going to just remove secure-policy from certification-
To post a comment you must log in.
Preview Diff
[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
In the context of server cert this makes sense, so +1.
Note, however, that the secure-policy package does NOT affect sudo, as it uses a different mechanism to grant passwordless execution (/etc/sudoers as opposed to a policy file we can just drop in a directory).
We need to think of another way of configuring sudo in these instances.
Our certification preseeds directly updated sudoers to allow this, depending on how you install systems we could come up with an equivalent way to configure it, but I fear it'll have to be outside our packages (or, we can add a postinst to the server provider package... fun).