You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My company is developing several nitro-based applications and one of the issues we've run into is that of reproducibility. Even if the source code for our application remains the same, it is possible to produce EIFs with different PCR0-2 values depending on the platform and version of the nitro-cli that was used when compiling said EIFs.
So, I've been updating our build pipeline to explicitly enforce and/or check for the correct platform, nitro-cli version, and build asset sha384sum values. During this process, however, I noticed that the blobs for release v1.3.4 on this repo do not match those installed by dnf aws-nitro-enclaves-cli-devel-1.3.4. Specifically, the init, linuxkit, and nsm.ko blobs are not the same.
My company is developing several nitro-based applications and one of the issues we've run into is that of reproducibility. Even if the source code for our application remains the same, it is possible to produce EIFs with different PCR0-2 values depending on the platform and version of the nitro-cli that was used when compiling said EIFs.
So, I've been updating our build pipeline to explicitly enforce and/or check for the correct platform, nitro-cli version, and build asset sha384sum values. During this process, however, I noticed that the blobs for release
v1.3.4
on this repo do not match those installed bydnf aws-nitro-enclaves-cli-devel-1.3.4
. Specifically, theinit
,linuxkit
, andnsm.ko
blobs are not the same.The
sha384sum
values for the gh x86 blobs are:The
sha384sum
values for the dnf x86 blobs are:Just thought I would let y'all know in case anyone runs into a similar issue.
The text was updated successfully, but these errors were encountered: