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
When using enki genkey to create self-signed secure boot certificates, all certs have the exact same name (CN), provided through the NAME parameter for the function. This makes it very hard to discern the different certificates, other than via the file name. It also doesn't properly show which certificates are issued by which other certificates, as they're all named the same.
Please adjust the logic for self-signed certificates to set proper names. For example:
"/CN=%s - PK/"
"/CN=%s - KEK/"
"/CN=%s - DB/"
The text was updated successfully, but these errors were encountered:
When using
enki genkey
to create self-signed secure boot certificates, all certs have the exact same name (CN), provided through theNAME
parameter for the function. This makes it very hard to discern the different certificates, other than via the file name. It also doesn't properly show which certificates are issued by which other certificates, as they're all named the same.Please adjust the logic for self-signed certificates to set proper names. For example:
The text was updated successfully, but these errors were encountered: