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

Support for /sys/class/dmi/id/product_uuid #268

Open
iansltx opened this issue Dec 29, 2021 · 15 comments
Open

Support for /sys/class/dmi/id/product_uuid #268

iansltx opened this issue Dec 29, 2021 · 15 comments

Comments

@iansltx
Copy link

iansltx commented Dec 29, 2021

Trying to use osquery (as part of Vanta Agent) and they need this file to exist and be populated. With open firmware, the file doesn't exist at this point, and the machine in question doesn't seem to have a proprietary firmware equivalent to work with (lemp10).

Happy to hack on this, but not sure where to start.

@crawfxrd
Copy link
Member

Why? What does Vanta use the UUID for?

Set by smbios_system_set_uuid() in coreboot.

@iansltx
Copy link
Author

iansltx commented Dec 29, 2021

Unique device ID for asset management, more or less. Standard compliance stuff.

@iansltx
Copy link
Author

iansltx commented Dec 30, 2021

Same problem, different vendor (also using coreboot), slightly different application: https://forums.puri.sm/t/coreboot-populating-sys-class-dmi-id-product-uuid/7506

@iansltx
Copy link
Author

iansltx commented Feb 3, 2022

Apologies for bumping this without much info, but looks like we can't use a kernel module to get around this, and I'm getting flak on allowing new hires to spec System76 machines until this gets fixed, as anything they pick is likely Open Firmware only at this point and other vendors' firmware includes the entry :/

@frankk74
Copy link

frankk74 commented Feb 22, 2022

This might or might not be a related issue:

acidanthera/bugtracker#711

Seems this might be a buikd issue?

Same issue from corporate. If we can't track it.

@crawfxrd
Copy link
Member

crawfxrd commented Jun 8, 2022

3mdeb's solution for Dasharo: https://review.coreboot.org/c/coreboot/+/64639

@antonshmakov
Copy link

Any way the solution above is applicable to original problem? Having the exact same issue -- trying to activate Vanta Agent on Lemur Pro (lemp11)

@colinbird
Copy link

Also having this issue on brand new Gazelle

@allan-simon
Copy link

same issue here with the gazelle and vanta

@allan-simon
Copy link

allan-simon commented Jan 31, 2023

seems it's about implementing the method smbios_system_set_uuid in https://github.com/system76/coreboot/

with something like

void smbios_system_set_uuid(u8 *uuid)
{
    memcpy(uuid,  UUID_DEFINED_BY_A_COMPILER_CONSTANT, 16);
}

@scottbisker
Copy link

Having a similar issue on an oryx pro 10 as well.

@fetherolfjd
Copy link

fetherolfjd commented May 1, 2023

Just ran into this as well attempting to install the Vanta agent on Oryx Pro.

@crawfxrd
Copy link
Member

system76/coreboot#182 will enable support for reading it from a CBFS file. firmware-update will then need to be updated to either copy it from the current firmware, or generate it if it doesn't exist, and then inject it into the new firmware image before flashing it.

@tupshin
Copy link

tupshin commented Oct 3, 2024

This is blocking me from using a system76 laptop with the Vanta agent, needed for hipaa/sox compliance. Makes it impossible to use them for corporate/startup activities

@iansltx
Copy link
Author

iansltx commented Oct 3, 2024

FWIW it's entirely possible to have an alternative remediation to "our systems all check into Vanta" and still be compliant. We got SOC2 Type II, via Vanta, with multiple System76 boxes, this way. You just have to document your controls. Same with HIPPA (disclosures apply that IANAL but Vanta should tell you the same thing).

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

No branches or pull requests

9 participants