Disable UI-based OTA updates if root file system is writable
Bug #1466125 reported by
Tony Espy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu system image |
Triaged
|
Wishlist
|
Barry Warsaw | ||
Bug Description
As it's possible for end-users of pre-installed Touch devices to make their file system writable *and* we know that this can lead to broken systems if new packages are installed via apt, we should prevent UI-based OTA updates from being applied. The UI should provide a clear explanation of why OTA updates are non-installable.
As discussed, it should be possible to use the command-line client to apply updates, and if used, a simple warning should be output.
This is being filed as of OTA4, based on the vivid-overlay PPA.
| tags: | added: client |
| Changed in ubuntu-system-image: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| assignee: | nobody → Barry Warsaw (barry) |
| milestone: | none → 3.1 |
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
Revision history for this message
| Mateo Salta (mateo-salta) wrote | #2 |
| Changed in ubuntu-system-image: | |
| milestone: | 3.1 → 3.2 |
To post a comment you must log in.
First, the problem isn't specific to the rootfs being *currently* writable. The problem exists if the rootfs has *ever* been marked writable (and modified).
Second, as discussed elswhere in mail, it would be better to force a full update in this case, *not* refuse to update the system. The Ubuntu Phone model is that users should receive updates automatically and seamlessly; while users can fiddle with their filesystem, we probably /don't/ want to leave those users islanded on the currently-installed image version forever, but instead propose a full update, possibly with appropriate caveats. This will clobber any (unsupported) local modifications but at least won't leave them with an insecure and unsupportable device.