[crypto] Cryptolib versioning

[nasahlpa]

This commit adds a versioning concept to the cryptolib. cryptolib_build_info_t contains:

• released - is the CL version released or not?
• version - pinned version of the CL
• scm_revision_low/high - truncated commit hash of sw/device/lib/crypto

[nasahlpa]

Thanks @pamaury for helping me with this. An optimization would be to get rid of the new cryptolib_build_info script and instead use the existing build_info script. However, it seems that this script uses quite some hardcoded values (e.g., the template for the .c file etc) and I am not sure how to best tackle this.

[andreaskurth]

Thx @nasahlpa and @pamaury. Do I understand correctly that the default and current behavior is that the version is a rolling / non-frozen / not pinned / not formally released one? Can we make that explicit somewhere, so that we can very clearly distinguish between in-development and released versions?

[nasahlpa]

Thx @nasahlpa and @pamaury. Do I understand correctly that the default and current behavior is that the version is a rolling / non-frozen / not pinned / not formally released one? Can we make that explicit somewhere, so that we can very clearly distinguish between in-development and released versions?

Thanks for the remark, Andreas.

Yes, the CL is currently not released, this is also mentioned in the documentation. I've added a comment to the version field.

[johannheyszl]

do we need to try exclude /data/crypto_testplan.hjson ? probably not possible I guess

[nasahlpa]

Not really sure how to do this TBH :/

[johannheyszl]

Thanks @nasahlpa this is needed :)

[andreaskurth]

Thanks for implementing my feedback, @nasahlpa. LGTM!