G'day, I've only just gotten started using BlueBuild so this seems like a silly question, and I can't seem to find any proper (at least, up to date) tutorial/documentation that goes over this step specifically, but For the longest time now, for my repo I've had to upload both my MOK.der and MOK.priv keys publicly to get successful builds. Naturally, I shouldn't do this, and I should make the MOK.priv key a repo secret so it builds without needing to upload the private key file. However, I'm unsure what to name the secret, or how to edit any scripts so that the build action reads the secret. Making secrets named MOK_PRIV and SECURE_BOOT_PRIV_KEY, with the MOK.priv key inside, doesn't do anything. Again, this may be completely trivial and not appropriate for this channel, and I apologise if that's the case, I'm just looking for help with the one step I haven't completely wrapped my head around yet.

message has been deleted

Yeah, you'll want to store that private key in a secret for the repo (and also somewhere else secure). You can follow how we [do it with our base images](https://github.com/blue-build/base-images/blob/9f6d041980917b1576dd234c7fa5492704b6f99a/.github/workflows/build.yml#L63-L67)

That's strange, my build.yml didn't include that key extraction section. I copy-pasted it and tried running it and got a base64: invalid input error My image is based on the base-images repo & fedora-base-nvidia image from a couple weeks ago, if that helps with anything

Check our workflow again. You have to do a manual checkout of your code and disable checkout on our action.

Thank you so much for your help! I'm terribly sorry for the bother

message has been deleted

No bother at all