-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verifying signed OTA fails #291
Comments
Can you post a link to the OTA? Or if it's not publicly available, can you extract the OTA with:
and post the output of:
I'm thinking either the |
I've run the command you asked for. Here is the output. I've captured the output to a logfile because it was too long. |
Thanks. Yep, so it's just hitting avbroot's internal limit. (The limit exists so that a corrupt/malicious OTA can't cause avbroot to use up the entire system's memory.) I'll increase the limit and release a new version of avbroot. |
Fixes: #291 Signed-off-by: Andrew Gunnerson <[email protected]>
Fixes: #291 Signed-off-by: Andrew Gunnerson <[email protected]>
Thank you for the update! I will try it again when I get home. |
No problem! 3.2.1 will be released in a few minutes with the change. |
What are the conditions for an OTA zip to be properly signed? Does it require a specific configuration when compiling the OTA zip first? I tried to sign the OTA zip for DerpFest for my device but trying to verify it back produces this error:
I wasn't sure what this error meant.
The text was updated successfully, but these errors were encountered: