Sequence files

See merge request !16

Add constraints to the schemas to strengthen validation even more where
possible.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Issue a deprecation warning when we detect a deprecated sequence file being
used.

We cannot deprecate ACS IR v1.0 sequence file as it is identical to the ACS
IR v2.0 BET-0 one.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

This is the same sequence file as ACS-IR v1.0 but we capture it for
completeness. Update the identification database accordingly.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Remove seq files

See merge request !15

The ACS build scripts use the sequence files from the bbr-acs repository.
Remove the unused EBBR and SBBR sequence files from the parser repository
to avoid confusion.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Fix a bug when using junit output

See merge request !14

Correct the name of the module being looked for in the assert at the
beginning of the junit output function.

Signed-off-by: Drew Reed <Drew.Reed@arm.com>

Add an SIE configuration

See merge request !12

Added support for outputing results in junit format

See merge request !13

Add a configuration to process SCT results from the Security Interface
Extension ACS.

The rules in this new configuration can override tests results with a new
`KNOWN RPMB LIMITATION' result.

Add the necessary enums to our schema and adjust the sequence files
database to use the new configuration automatically when the SIE ACS is
detected.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Drew Reed authored Jul 23, 2021 and Drew Reed committed Jul 14, 2022

Added new --junit command line option to instruct the script to output
the results in junit format for easy inclusion in CI systems

Signed-off-by: Drew Reed <Drew.Reed@arm.com>

No functional change.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Let's make sure our sample is correct.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

For the moment we have only the EBBR.yaml configuration. Command line does
still take precedence. No functional change.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

We add a schema and a `--validate-seq-db' command line option to validate
our sequence files database, now that it is in YAML format.
We call the validation from `make check'.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Let's use YAML as much as we can as we can better validate it and extend
it.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

To prepare for adding more validation schemas, create a dedicated folder
for our schemas.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

The SCT in the ACS-IR 2.0 Alpha has been updated; add some rules to triage
the results accordingly in preparation of IR 2.0.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

IR 1.1 certifications should use the ir1 branch so that development can
continue on the main branch.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Deal with empty config gracefully. This allows to pass e.g. /dev/null as
config without crashing the parser.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

schema + BBSR seq file

See merge request !11

Add the BBSR sequence file from the Security interface extension ACS
v21.10_SIE_REL1.0.

While at it, fix sequence files permissions.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

We know all the valid values for many fields of the configuration rules.
Refine the schema to constrain the EBBR.yaml config file a bit more.

This means we are giving up the ability to mention only a sub-string for
those fields in the config file, which we were not doing anyway.

Also, forbid additional properties where we can.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Schema + minors

See merge request !10

- Add a jsonschema describing requirements on the configuration file.
- Add a --validate-config and a --schema parser options to make use of the
  schema.
- Add a check for the EBBR.yaml configuration in `make check'.
- Document in the README.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Even tparm() can fail on some platforms; make the whole colors probing part
more robust by catching exceptions.

Reported-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

setafb must be bytes, as we will decode() it later on.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Colors and SetState

See merge request !9

Add red/yellow/green colors to more messages.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Re-classify warnings issued by the SCT regarding SetState() returning
unsupported as known ACS limitations and drop the known SCT limitation
category. Also, add a reference to the corresponding edk2-test bug entry.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

This fixes some crashes when using e.g. `--uniq --print --fields <list
without count in it>'.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Colors and plurals

See merge request !8

Deal with plural in a better way, in a couple of additional non-debug
places. While at it, update the README.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Now that we have colors, use them in our summary line. While at it, deal
more nicely with plurals.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

Add some colors to our logging messages. We convert a couple of remaining
cases not using the logging facility for error messages.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

New "known sct limitation"

See merge request !7

A specific case where SetState() return "unsupported" makes the SCT emit a
warning. As this is a valid return value, add a rule to force this warning
as "known sct limitation".

While at it, document this new "known sct limitation" category in the
README.

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>

New "known u-boot limitation" revealed by ACS-IR v1.0

See merge request !6