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

[RFE] Include the image signing key in an accessible place in every system #1115

Open
neilmayhew opened this issue Jul 16, 2023 · 4 comments
Labels
kind/feature A feature request

Comments

@neilmayhew
Copy link

Current situation

I would like to be able to verify images and other artifacts downloaded using a Flatcar system. Currently, this requires fetching the signing key from the internet. However, presumably the update engine is verifying images. It would be very helpful to have access to the same key instead of downloading a separate copy, as it would be both secure and convenient.

Impact

It makes writing scripts (eg the one in #21) easier and more secure.

Ideal future situation

The signing key is available in a documented and stable location.

Implementation options

/etc/flatcar/Flatcar_Image_Signing_Key.asc

@neilmayhew neilmayhew added the kind/feature A feature request label Jul 16, 2023
@pothos
Copy link
Member

pothos commented Jul 17, 2023

Thanks, sounds like a good idea - so far the key was part of the flatcar-install script only.
In the mean time you can extract it there: GPG_KEY=$(tr '\n' '_' < /usr/bin/flatcar-install | grep -Po 'GPG_KEY="\K.*?(?=")' | tr '_' '\n')

@neilmayhew
Copy link
Author

Thanks! I knew it must be somewhere but I didn't think of checking the install script.

Does the update engine verify signatures, too? If so, I assume the key isn't as easily extracted because it's a compiled binary rather than a script.

@pothos
Copy link
Member

pothos commented Jul 17, 2023

The update-engine key is currently separate and only used for the update payloads, you can find it under /usr/share/update_engine/update-payload-key.pub.pem. I hope that one day this is a single key to avoid the confusion between signing images and updates.

@neilmayhew
Copy link
Author

I see. Thanks for clarifying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature A feature request
Projects
Development

No branches or pull requests

2 participants