Generate fake root certs for autotest via qemu

Generate fake root certs for autotest via qemu

mod_image_for_test.sh now passes the target architecture to the subscripts
mod_for_test_scripts/710enableAuthTesting generates the /etc/fake_root_cert
databases by running nsscertutil under QEMU.

BUG=3310
TEST=Built autotest enabled images for x86 and arm.  On arm, the browser no
longer crashes trying to read the fake root certs.

[jneddo1, 2010-07-19 19:34:54]

Fixed a script error

[Uday, 2010-07-19 22:18:44]

On 2010/07/19 19:34:54, jneddo1 wrote:

I am getting:
nsscertutil: function failed: security library: invalid arguments while
executing nsscertutil command when running the script.

[Uday, 2010-07-19 22:40:04]

On 2010/07/19 22:18:44, Uday wrote:

Can i know whther u are running a debug build of sqlite or a release build of
sqlite?

[Olof Johansson, 2010-07-20 14:30:41]

LGTM, the problems I had earlier with using qemu seems to be gone. Tested OK
here.

Adding Chris as reviewer since the original script was done by him.

[Chris Masone, 2010-07-20 16:21:26]

http://codereview.chromium.org/2878033/diff/3001/4001
File mod_for_test_scripts/710enableAuthTesting (right):

http://codereview.chromium.org/2878033/diff/3001/4001#newcode29
mod_for_test_scripts/710enableAuthTesting:29: mv -f "${TMP_CERT}"
"${ROOT_FS_DIR}/${TMP_CERT}"
mktemp just generates filenames, so this mv is odd.  I think you can just
replace the "-p /tmp" above with "-p ${ROOT_FS_DIR}/tmp" and get rid of these.

[jneddo1, 2010-07-20 18:11:36]

On 2010/07/20 16:21:26, cmasone wrote:
> http://codereview.chromium.org/2878033/diff/3001/4001
> File mod_for_test_scripts/710enableAuthTesting (right):
> 
> http://codereview.chromium.org/2878033/diff/3001/4001#newcode29
> mod_for_test_scripts/710enableAuthTesting:29: mv -f "${TMP_CERT}"
> "${ROOT_FS_DIR}/${TMP_CERT}"
> mktemp just generates filenames, so this mv is odd.  I think you can just
> replace the "-p /tmp" above with "-p ${ROOT_FS_DIR}/tmp" and get rid of these.

If I change this to:
TMP_KEY=$(mktemp -p ${ROOT_FS_DIR}/tmp "${CERT_NAME}.key.XXXXX")

Then TMP_KEY get set to something like
/home/justin/trunk/src/build/images/tegra2-dev-board/0.7.55.2010_07_15_0948-a1/rootfs/tmp/mock_server.key.s65Kx
whereas right now it would just be /tmp/mock_server.key.s65Kx

The script uses the value in TMP_KEY inside the rootfs chroot.  Not the build
chroot, but a new chroot in the rootfs.  I needed the filename and the temporary
files, so I called mktemp to make the files, then moved them to the chroot so
the path would still work.

[Chris Masone, 2010-07-21 17:08:57]

On 2010/07/20 18:11:36, jneddo1 wrote:
> On 2010/07/20 16:21:26, cmasone wrote:
> > http://codereview.chromium.org/2878033/diff/3001/4001
> > File mod_for_test_scripts/710enableAuthTesting (right):
> > 
> > http://codereview.chromium.org/2878033/diff/3001/4001#newcode29
> > mod_for_test_scripts/710enableAuthTesting:29: mv -f "${TMP_CERT}"
> > "${ROOT_FS_DIR}/${TMP_CERT}"
> > mktemp just generates filenames, so this mv is odd.  I think you can just
> > replace the "-p /tmp" above with "-p ${ROOT_FS_DIR}/tmp" and get rid of
these.
> 
> If I change this to:
> TMP_KEY=$(mktemp -p ${ROOT_FS_DIR}/tmp "${CERT_NAME}.key.XXXXX")
> 
> Then TMP_KEY get set to something like
>
/home/justin/trunk/src/build/images/tegra2-dev-board/0.7.55.2010_07_15_0948-a1/rootfs/tmp/mock_server.key.s65Kx
> whereas right now it would just be /tmp/mock_server.key.s65Kx
> 
> The script uses the value in TMP_KEY inside the rootfs chroot.  Not the build
> chroot, but a new chroot in the rootfs.  

Ah, this makes sense now.  Ok, so you basically need the path with
${ROOT_FS_DIR} prepended as well as without.

> I needed the filename and the temporary
> files, so I called mktemp to make the files, then moved them to the chroot so
> the path would still work.


LGTM

[Olof Johansson, 2010-07-22 15:18:19]

Committed.