817633 - FIPS tests do not run on Android

Status: NEW

(NSS :: Test, defect, P5)

Description

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

+++ This bug was initially created as a clone of Bug #772144 +++

We can re-do the cross-compilation by doing the following, in order to get the FIPS tests to run:

1. Require that a build of NSS be done for the host system, 
2. Require that the cross-build of NSS to Android pass NSS_HOST_PREFIX=<path to the host build>
3. Use $NSS_HOST_PREFIX/shlibsign instead of the in-tree shlibsign to sign the libraries.

Comment 1

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

From the patch in bug 772144: "Android doesn't support FIPS tests, because dladdr does not return a full path for implicitly loaded libraries."

Mike, do you have any suggestions here?

Comment 2

[Mike Hommey [:glandium]]

You're essentially screwed. The Android system linker just doesn't store the full path for any library (not even the non dlopen()ed ones).
It works in firefox because we use our own linker for our libs.

Comment 3

[Brian Smith (:briansmith, :bsmith, use NEEDINFO?)]

(In reply to Mike Hommey [:glandium] from comment #2)
> You're essentially screwed. The Android system linker just doesn't store the
> full path for any library (not even the non dlopen()ed ones).
> It works in firefox because we use our own linker for our libs.

It seems like this is a very solvable problem as long as we're willing to make some assumptions that are reasonable for Android apps that might not be so reasonable on other platforms.

On Android, do we actually need dladdr to return the full path for these libraries? We should be able to figure out the base directory $BASE of the app. For the vast majority of apps, the NSS shared libraries are always going to be at some path $BASE/$something. From there, we can Couldn't we just have a build-time flag for Android builds that tells us $something, and then use some Android API (or environment variable) to determine $BASE?