BUG=5130
TEST=create a test image, boot it on a device, and run "sudo nsscertutil -d "sql:/etc/fake_root_ca/nssdb" -L -n FakeCert | less". Look at the section of the output marked "Validity:" and make sure the Not Before and Not After sections indicate dates that are 3 weeks apart
Change-Id: I67cf7e71027147f83c1bc916557bc06ef66fa0e0
Review URL: http://codereview.chromium.org/3075025
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.
Review URL: http://codereview.chromium.org/2878033
power_LoadTest will use this symlink to load a test extension at login.
BUG=None
TEST=power_LoadTest
Signed-off-by: Benson Leung <bleung@chromium.org>
Review URL: http://codereview.chromium.org/2877007
to handle changed command line arguments, and attempt
to make it resilient in the face of future changes.
TEST=Run script on fresh image; confirm that '-I eth_test' is present on the exec line of /etc/init/flimflam.conf
Review URL: http://codereview.chromium.org/2842023
This prevents the machine from suspending while it is being tested.
TEST=Modified an image for test and verified that powerd did not suspend.
BUG=chromium-os:3694
Review URL: http://codereview.chromium.org/2620008
BUG=3283
TEST=Tested by running mod_image_for_test and checking the stateful partiton
on the resulting image and verifying that these files exist in the correct
locations.
Review URL: http://codereview.chromium.org/2107013
on the device under test and to use a not-normally-generated interface name, so that use of add-on ethernet devices is not affected in normal operation.
BUG=2962, 2941
(dup of 1810013, git goofiness)
Review URL: http://codereview.chromium.org/1826003
After discussing with drewry, we can't come up with a better way to inject these root certs. We considered putting them on the stateful partition, but that opens up an avenue of attack (if you can get a root cert into the magic directory, then you can MITM login). Thus, we put it on the rootfs instead. The script that sets up the hashes for vboot will verify that this directory is not present in production images. That work is tracked here: http://code.google.com/p/chromium-os/issues/detail?id=2693
Review URL: http://codereview.chromium.org/1566055
It worked when all mod for test script works inside chroot. But not anymore since "df /" now report the host disk space, not the rootfs.
Review URL: http://codereview.chromium.org/1130005
Get rid of chroot inside this script, and not mounting mod_for_test_scripts into rootfs any more.
The reason caused the failure here is once you chroot into the mounted rootfs directory, all binaries were searched inside the rootfs. But all binaries inside the arm rootfs was for arm hardware, so not executable on the host linux machine(intel).
Review URL: http://codereview.chromium.org/845007
- Rev chromeos-systemtests, and add fio as a dependency.
- Add fio into the image during mod_image_for_test.sh
Review URL: http://chromereview.prom.corp.google.com/1180028
git-svn-id: svn://chrome-svn/chromeos/trunk@297 06c00378-0e64-4dae-be16-12b19f9950a1
