tree b3aa65dbd18fa50718c6c7a17329bc89dfd89293
parent 15b78cf68518521fc33a34b57c4d343f160d5842
author Mary Ruthven <mruthven@google.com> 1521150761 -0700
committer chrome-bot <chrome-bot@chromium.org> 1521520470 -0700

cr50_stress_experimental: add firmware_Cr50RMAOpen

Cr50 has RMA Open support. This change adds a test to verify different
RMA features. It verifies the opening, rate limiting, and challenge
generation through the AP and command line interfaces.

There are two sets of keys images can be built with: test and prod. At
some point prepvt flagged images will use test keys and prod flagged
will use prod keys. The test cannot generate authcodes for prod keyed
images, so it will verify that test authcodes will not open Cr50. If the
test sees Cr50 is using test keys, it will verify that RMA open succeeds
with the generated authcodes. Since the test cannot verify RMA open
succeeds with prod keys, images with prod keys will need to be verified
manually. This test can still be used to verify the challenge rate
limiting and other basic functionality.

This test will also fail if it sees a MP signed prod flagged image with
test keys.

BUG=none
BRANCH=none
TEST=run on 2.2, 1.2, and 3.3 built with test keys and one with prod
keys

Change-Id: Ie1aac0a6a385e1586fc468c0563eba64d20a5a79
Signed-off-by: Mary Ruthven <mruthven@google.com>
Reviewed-on: https://chromium-review.googlesource.com/964864
Commit-Ready: Mary Ruthven <mruthven@chromium.org>
Tested-by: Mary Ruthven <mruthven@chromium.org>
Reviewed-by: Wai-Hong Tam <waihong@google.com>