Merge lp:~shnatsel/unattended-upgrades/plymouth-message-fix into lp:~ubuntu-core-dev/unattended-upgrades/ubuntu
Proposed by
Sergey "Shnatsel" Davidoff
Status: | Work in progress |
---|---|
Proposed branch: | lp:~shnatsel/unattended-upgrades/plymouth-message-fix |
Merge into: | lp:~ubuntu-core-dev/unattended-upgrades/ubuntu |
Diff against target: |
14 lines (+4/-0) 1 file modified
debian/postinst (+4/-0) |
To merge this branch: | bzr merge lp:~shnatsel/unattended-upgrades/plymouth-message-fix |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sergey "Shnatsel" Davidoff (community) | Disapprove | ||
Colin Watson | Needs Information | ||
Review via email: mp+44484@code.launchpad.net |
Description of the change
Partially fixed sending messages to Plymouth (race condition still not handled)
To post a comment you must log in.
Unmerged revisions
- 154. By Sergey "Shnatsel" Davidoff
-
fixed sending messages to Plymouth (except for race condition)
Thanks for your suggestion.
I'm thoroughly confused about this. Making this script setuid is definitely not going to be allowed - it should just be started with the proper privileges in the first place. However, as far as I can tell, all the code paths that start unattended- upgrade- shutdown do so as root, and plymouthd explicitly refuses messages from non-root users. So I don't quite understand what's going on here, and how dropping to a non-root user might help.