Image signing has to happen on the native host computer and not
in any of the VMs so a powershell script was created to allow
automation of the 'beta' signing key. This script fully automates
the signing and also staging of images to the testing environment.
This will need to be revised into a linux script for final
deployment as CI is done in a linux environment, but "day to day"
signature testing is done in the development environment, thus
this version of the script was prioritized.
Shouldn't be too hard to extend this to the linux environment,
I think Windows is the harder one to integrate.
fido-signer now automatically recognizes xous images and
patches the signature with the updated signature record,
as well as re-generating the corresponding .uf2 file.
auth_data actually changes with each signing operation (ostensibly
to prevent replay of signatures coming from tokens) so it has
to be presented as data parallel to the signature, instead of
as a static filed baked into the key header.
This commit revises the header record to reflect this organizatio
of data and also revises the signature check to be in-line
with the protocol.
have to absorb a version change due to xous-semver change
might as well also update the utra/svd generator dependencies
since that's been held off for a long time now.
- poc signing flow using hardware key is demonstrated
- tested with signature verification using python script
- beta key committed to tree (the "secret" key just contains
the key identifier, not the key itself; the key resides in the
token)
this is the agnostic version of all of the board targets, which
allows the boot1 to lookup based on the current configuration
which configurations to apply.
I think I've talked myself into giving away $0.20 of parts with
every dabao board so that everyone can run at full frequency.
Originally I thought I'd limit to the minimal configuration with
low frequency operation but since this is the main developer
platform all the benchmarks and first impressions will come
through this board. Crippling it with a slower clock frequency
by omitting the supplementary digital regulator seems
short-sighted, even if it means up slightly subsidizing things
with this extra cost.