Skip to content

Release v4.0.1

Latest

Choose a tag to compare

@prabhu prabhu released this 05 Oct 10:43
fc39d12

blint 4.0.1 is a patch release. It adds the Android native work that was finished just after 4.0.0 shipped.

Android: native methods bound through JNA

Apps that reach Rust or C through JNA direct mapping, which is how uniffi bindings work, declare native methods that no JNI export or RegisterNatives table answers. With the disassemble flag, blint now reads the Native.register calls in the dex and binds each of those declarations to the same-named export in the library the call registers. These rows are labelled confirmed_by jna_direct.

A row binds only when three things hold. The call names the declaring class, libjnidispatch.so ships for that ABI, and exactly one library exports the name. If two libraries export the name and nothing proves which one is meant, the row stays ambiguous and lists both. On the reference corpus this binds 6,045 previously unbound declarations in Fennec and Element, and every address matches llvm-nm.

The app call graph now draws a JNI edge for every bound declaration. Before this release the edges were taken from the metadata listing, which is capped at 256 entries per ABI, so large apps lost edges.

A proportionate 16 KB page finding

CHECK_ANDROID_PAGE_16K reports the Google Play 16 KB page requirement, which applies to apps that target API 35 or newer. A library scanned on its own, such as one taken from a system image, belongs to no known app. It now gets the finding at medium instead of high. Apps that target API 35 or newer still see it at high.

Documentation

A new Android native guide, docs/ANDROID.md, explains what blint does with the native code in an APK or AAB. It covers the per-ABI facts and rules, framework identification in the SBOM, every JNI join list and label, and the groups the join cannot reach yet.

Full changelog: v4.0.0...v4.0.1