History log of /external/vboot_reference/tests/gen_fuzz_test_cases.sh
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
a1d9fe6eecf82540d31d34bba988e4838d295302 05-Sep-2014 Bill Richardson <wfrichar@chromium.org> futility: stop using the symlink names in utility scripts

We still create the symlinks (FOO -> futility), but this
change invokes those built-in functions with "futility FOO ..."
instead of using the FOO symlink.

Note that the scripts/ directory is unchanged. That's a
separate CL, since we don't have tests for that.

BUG=chromium:231547
BRANCH=ToT
TEST=make runtests

In addition to running "make runtests", I temporarily
modified the Makefile to avoid creating the symlinks at all.
The tests still passed.

Change-Id: I96863259b9df02a3611f759a7509bf4090ae03e8
Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/216717
Reviewed-by: Randall Spangler <rspangler@chromium.org>
/external/vboot_reference/tests/gen_fuzz_test_cases.sh
3e3790d00827e75d39b77a14bca2756a14a51b3c 15-Jul-2014 Bill Richardson <wfrichar@chromium.org> Install and use futility when running tests

As we build features into futility, the standalone executables disappear.
Tests that invoke those executables will need to invoke futility instead.

BUG=chromium:224734
BRANCH=ToT
TEST=make runtests

Signed-off-by: Bill Richardson <wfrichar@chromium.org>
Change-Id: I75230f6901aab8d978fa5d12505c243e1c90c938
Reviewed-on: https://chromium-review.googlesource.com/207926
Reviewed-by: Randall Spangler <rspangler@chromium.org>
/external/vboot_reference/tests/gen_fuzz_test_cases.sh
844bce57471153664c78993dab453e87891bb969 16-Jan-2013 Randall Spangler <rspangler@chromium.org> Run some tests under qemu when cross-compiling

BUG=chromium-os:26317
BRANCH=none
TEST=manual

sudo FEATURES=test emerge vboot_reference
FEATURES=test emerge-link vboot_reference chromeos-u-boot chromeos-installer
FEATURES=test emerge-daisy vboot_reference chromeos-u-boot chromeos-installer
make && make runtests (both inside and outside chroot)

Change-Id: Ie829e375736ce0df46ddd5a3345efb0ca7e33aba
Signed-off-by: Randall Spangler <rspangler@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/41317
/external/vboot_reference/tests/gen_fuzz_test_cases.sh
a222fbc00eb470c104602be262b97c9c8c7be7a2 30-Sep-2010 vbendeb <vbendeb@chromium.org> Fix test suite deficiencies.

While trying to debug/test some vbutil_kernel changes
(coming in a different CL) it was noticed that this utility
is not covered by tests, and the script which runs it to set
up further testing (tests/gen_fuzz_test_cases.sh) fails
because of the key format mismatch.

Some investigation has shown that this was left behind when
vboot_reference key storage format was changed.

To make gen_fuzz_test_cases.sh work again a new set of test
keys is required, the keys are generated by
tests/gen_test_keys.sh. This utility had to be changed to
generate the proper set of wrapped public and private keys.

Actually code in tests/gen_test_keys.shgenerate_keys() is
copied in pasted in many scripts in this tree, this has to
be refactored, but under a different CL.

Once the changes were made, two scripts were run:
./tests/gen_test_keys.sh
./gen_test_cases.sh

resulting in the new and updated keys generated.

firmware/stub/tpm_lite_stub.c was edited to fix compilation
warning issued when compiling with debugging enabled.

Change-Id: I26a45cbad00d21a29195f2a89b4df7d3559133fe

BUG=chromium-os:7178
TEST=described below

The following commands succeed:

vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
make
make runtests
./tests/gen_fuzz_test_cases.sh
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

note that ./tests/gen_fuzz_test_cases.sh was failing
before this change.

The upcoming CL modifying vbutil_kernel will make sure
gen_fuzz_test_cases.sh is executed when tests are run and
will enhance it to cover vbutil_kernel testing.

Review URL: http://codereview.chromium.org/3423022
/external/vboot_reference/tests/gen_fuzz_test_cases.sh
0ec7078d5b9995bd2fd0de445c5ec444793dc26c 30-Jun-2010 Gaurav Shah <gauravsh@chromium.org> Rewrite gen_fuzz_test_cases.sh script to use new signing utilities.

TEST=Generated images verify successfully using right keys.

Review URL: http://codereview.chromium.org/2836036
/external/vboot_reference/tests/gen_fuzz_test_cases.sh
f5db4b86fa5569285dfc8373fd8977e1998b8066 27-May-2010 Bill Richardson <wfrichar@chromium.org> Modifying the kernel_utility tool to create our magic blob.

For the --generate operation, the --in <file> option is gone and there are
three new required options:

--vmlinuz <file> Embedded kernel image
--config <file> Embedded kernel command-line parameters
--bootloader <file> Embedded bootloader stub

This takes the specified kernel, extracts the 32-bit component, and combines
that with the configuration file (essentially just the kernel cmdline
string) and the bootstub image . The resulting blob is signed and ready to
put in a kernel partition.

There's also an optional --padding parameter, to specify how much extra
(unsigned) space to leave between the signature header and the kernel blob.
The default is 0x4000, which is about four times as much needed when using
the largest signature size we currently support.

Review URL: http://codereview.chromium.org/2283005
/external/vboot_reference/tests/gen_fuzz_test_cases.sh
445925fe0f11280c585879247eada43de32090ca 20-Mar-2010 Gaurav Shah <gauravsh@chromium.org> Vboot Reference: Spring cleaning of test scripts.

Moved duplicated code to "common.sh". Make directory detection more robust.

Review URL: http://codereview.chromium.org/1101004
/external/vboot_reference/tests/gen_fuzz_test_cases.sh
ccaa90f73568653bd11998df3b5a42257bccffd6 18-Mar-2010 Gaurav Shah <gauravsh@chromium.org> Add fuzz testing driver programs for kernel and firmware verification.

The driver programs are useful in quick and dirty fuzz testing of the verification code with blind smartfuzzers like Bunny (http://code.google.com/p/bunny-the-fuzzer/).

Also fixes a bug with image generation in kernel_utility.

Tests: All existing tests still pass. VerifyKernel() and VerifyFirmware() can successfully verify images generated by {firmware|kernel}_utility.

Review URL: http://codereview.chromium.org/975007
/external/vboot_reference/tests/gen_fuzz_test_cases.sh