Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generate signing keys using OpenSSL utilities #806

Closed
BeataZdunczyk opened this issue Apr 17, 2024 · 5 comments
Closed

Generate signing keys using OpenSSL utilities #806

BeataZdunczyk opened this issue Apr 17, 2024 · 5 comments
Assignees

Comments

@BeataZdunczyk
Copy link
Member

BeataZdunczyk commented Apr 17, 2024

Brief summary

Utilize OpenSSL command line utilities to generate the necessary signing keys for the capsule update process.

Additional context
Create a list of supported algorithms and key sizes with links to source code or edk2 documentation, along with OpenSSL commands to create those.

@SergiiDmytruk
Copy link
Member

SergiiDmytruk commented Aug 12, 2024

No Jira task for this, or is it part of some task named differently?

Update: I found it.

@SergiiDmytruk
Copy link
Member

coreboot PR (capsule.sh update): Dasharo/coreboot#552
docs PR: Dasharo/docs#885

@philipandag
Copy link

I have managed to create all the required certificates using the documentation and to create a capsule. I can not test if using the generated keys in capsule.sh make would work because error: current board configuration lacks support of update capsules in the case of building for either qemu or vp66xx. Signing the capsule and verifying the signature would be the last step of verifying if everything works. Do you know any device which supports the capsules or if I can easily change it in the config?

@philipandag
Copy link

philipandag commented Aug 30, 2024

I have been able to sign the capsule using the generated keys using capsule.sh make and decode and verify it using payloads/external/edk2/workspace/Dasharo/BaseTools/BinWrappers/PosixLike/GenerateCapsule which probably means that the instructions are valid. The only issue is with selecting the CA to be used by openssl which looks for the CA at /etc/ssl/pki/CA by default on my and @JanPrusinowski's systems.

@philipandag
Copy link

Here are all the artifacts I have generated in the process.
results.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants