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

A RPM package containing fdo_manufacturing_client #706

Open
jbenc opened this issue Dec 17, 2024 · 2 comments
Open

A RPM package containing fdo_manufacturing_client #706

jbenc opened this issue Dec 17, 2024 · 2 comments

Comments

@jbenc
Copy link

jbenc commented Dec 17, 2024

Currently, fdo_manufacturing_client is packaged in fdo-init.rpm. However, that package was specifically created to be injected into coreos installer's initramfs. There's no generic fdo_manufacturing_client rpm with a systemd service file etc.

@nullr0ute
Copy link
Contributor

The manufacturing process is designed to run once to generate a device/OV credential pair, and in fact for devices that already come with credentials created, say stored in a tpm2 module, it shouldn't actually be run at all.

Can you outline more details why you would need this as a separate package running as a service?

@jbenc
Copy link
Author

jbenc commented Dec 18, 2024

The intended use case is a bootable container (bootc). You need to be able to add the client when building the container (thus the need for an rpm package) and you need to be able to run it somehow. You're right it doesn't have to be via systemd; we may certainly brainstorm other ideas.

The main point is there's no on-device installer. The creation of the image happens off the device[*]. The role of the installer is replaced by the first boot; in the case of FDO, it would be the first (manufacturing) and the second (onboarding) boot.

[*] Now, it would be an interesting discussion whether the manufacturing step could be performed off the device, i.e. performed on a VM image from outside of the image. My reading of the specs is it's not supposed to be; on the other hand, it would be indistinguishable from the point of view of the rest of the FDO process, so it may not really matter. Unless you want to use a (possibly emulated) TPM. May be an interesting area for research.

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

No branches or pull requests

2 participants