Andrew Gunnerson
e929ecbe44
The author of ring recently announced that the library is no longer being maintained and fixes for security issues may be significantly delayed. Big thanks to Brian Smith for creating and maintaining the library for so long! This commit replaces ring with aws-lc, a cryptography library maintained by Amazon AWS. It seems to be well-regarded and is used by high-profile projects like rustls. It is also API-compatible with ring, so it is effectively a drop-in replacement. Unfortunately, we still cannot switch back to the RustCrypto SHA1 and SHA2 implementations because they are still significantly slower than ring and aws-lc on systems that do not support the SHA-NI extensions. https://rustsec.org/advisories/RUSTSEC-2025-0007 Signed-off-by: Andrew Gunnerson <accounts+github@chiller3.com>
End-to-end tests
avbroot's output file is reproducible for a given input file. e2e.toml lists some profiles for generating mock OTA images with unique properties and the expected checksums before and after patching. These tests use pregenerated, hardcoded test keys for signing. These keys should NEVER be used for any other purpose.
For each profile listed in the config, the test process will:
- Generate a mock OTA based on the specification
- Verify tha original OTA checksum
- Run avbroot against the OTA using
--magisk(with a mock Magisk APK) - Verify the patched OTA checksum
- Extract the AVB-related partitions from the patched OTA
- Run avbroot against the OTA again using
--prepatched - Verify the patched OTA checksum again
The default profiles shipped with the project mimic how various stock OTAs for Pixel devices are built. The generated mock OTAs have valid signatures and data structures for all components, but without any actual data where possible. For example, most files in the ramdisks are empty files. To ensure the mock OTAs cannot be mistakenly installed on a real device, the OTA metadata lists a fake device name in the preconditions section.
Running the tests
To test against the profiles listed in e2e.toml, run:
# To test all profiles
cargo run --release -- test -a
# Or to test against specific profiles
cargo run --release -- test -p pixel_v4_gki -p pixel_v4_non_gki