#11682 NORM 1.75-fi: Corrupted bootfw files are fatal to secure boot; ecfw updates are not
Zarro Boogs per Child
bugtracker at laptop.org
Sun Mar 11 18:41:09 EDT 2012
#11682: Corrupted bootfw files are fatal to secure boot; ecfw updates are not
-------------------------------------------+--------------------------------
Reporter: greenfeld | Owner: wmb at firmworks.com
Type: defect | Status: new
Priority: normal | Milestone: 1.75-firmware
Component: ofw - open firmware | Version: Development build as of this date
Resolution: | Keywords:
Next_action: review | Verified: 0
Deployment_affected: | Blockedby:
Blocking: |
-------------------------------------------+--------------------------------
Comment(by Quozl):
Replying to [comment:7 rsmith]:
> My personal feeling is that any errors should not prevent the laptop
from booting. Is there specific reasoning for a corrupted bootfw.zip
stopping the boot?
Reviewing the code, I don't see any specific reasoning. I don't remember
any reasoning; I wasn't as involved back then.
----
''firmware-up-to-date?'' detects incorrect size of proposed image and
calls ''.security-failure''.
''((fw-version))'' detects invalid version number of either the current
firmware or the proposed image, and calls ''.security-failure''.
''.security-failure'' shows sad face (''show-sad''), and calls ''security-
failure'', which delays 30 seconds and calls ''power-off''.
On the other hand, once a firmware update is committed to, if not enough
power present ''do-firmware-update'' merely skips the update.
--
Ticket URL: <http://dev.laptop.org/ticket/11682#comment:8>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system
More information about the Bugs
mailing list