pa-fazil
/
android_packages_modules_Virtualization
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
android_packages_modules_Vi.../compos/composd/native/Android.bp

18 lines
344 B
Plaintext
Raw Normal View History

Add native code for cert munging. Compsvc returns a self-signed cert (from Keystore), but we only want the public key. Extracting this in Rust is non-trivial, so instead we use existing support in BoringSSL in native code. (The details are copied from compos_key_cmd.cpp, which in turn were copied from the now-deleted FakeCompOS in odsign.) We could alternatively do this in compsvc itself, but I was slightly more reluctant to introduce native code there. Bug: 186126194 Test: Run composd_cmd twice, check it accepts the key pair it generated. Change-Id: I3faab9a7ada149d7f2776c2fb4d2656837c95e6f
2021-09-27 13:03:31 +00:00
package {
default_applicable_licenses: ["Android-Apache-2.0"],
}
rust_library {
name: "libcomposd_native_rust",
crate_name: "composd_native",
srcs: ["lib.rs"],
rustlibs: [
composd: prepare staging directory w/ libartpalette-system Output files are staged until they are fully generated, then move to the final location. The staging directory has a different SELinux context to prevent misuse, and should change when it's moved to the final directory. This change makes composd to follow the same setup, using libartpalette. As a result, the output are no longer stored in CompOS's own apexdata (which was not intentional). This change does not use bindgen, which seems have some difficulty to bridge `const char**` correctly. Neither cxx, since it doesn't seem to simplify the (already simple) call. Bug: 205750213 Test: See odrefresh produces output in the staging directory Change-Id: Ifc97b31a98052a31209556449d1642089a8c0e2e
2021-12-04 00:30:04 +00:00
"libanyhow",
"liblibc",
Add native code for cert munging. Compsvc returns a self-signed cert (from Keystore), but we only want the public key. Extracting this in Rust is non-trivial, so instead we use existing support in BoringSSL in native code. (The details are copied from compos_key_cmd.cpp, which in turn were copied from the now-deleted FakeCompOS in odsign.) We could alternatively do this in compsvc itself, but I was slightly more reluctant to introduce native code there. Bug: 186126194 Test: Run composd_cmd twice, check it accepts the key pair it generated. Change-Id: I3faab9a7ada149d7f2776c2fb4d2656837c95e6f
2021-09-27 13:03:31 +00:00
],
composd: prepare staging directory w/ libartpalette-system Output files are staged until they are fully generated, then move to the final location. The staging directory has a different SELinux context to prevent misuse, and should change when it's moved to the final directory. This change makes composd to follow the same setup, using libartpalette. As a result, the output are no longer stored in CompOS's own apexdata (which was not intentional). This change does not use bindgen, which seems have some difficulty to bridge `const char**` correctly. Neither cxx, since it doesn't seem to simplify the (already simple) call. Bug: 205750213 Test: See odrefresh produces output in the staging directory Change-Id: Ifc97b31a98052a31209556449d1642089a8c0e2e
2021-12-04 00:30:04 +00:00
shared_libs: [
"libartpalette-system",
],
Add native code for cert munging. Compsvc returns a self-signed cert (from Keystore), but we only want the public key. Extracting this in Rust is non-trivial, so instead we use existing support in BoringSSL in native code. (The details are copied from compos_key_cmd.cpp, which in turn were copied from the now-deleted FakeCompOS in odsign.) We could alternatively do this in compsvc itself, but I was slightly more reluctant to introduce native code there. Bug: 186126194 Test: Run composd_cmd twice, check it accepts the key pair it generated. Change-Id: I3faab9a7ada149d7f2776c2fb4d2656837c95e6f
2021-09-27 13:03:31 +00:00
apex_available: ["com.android.compos"],
}