Clavem

Hardware ID

A hardware ID is a raw identifier read from a computer's operating system or firmware, such as the macOS hardware UUID or the Linux machine ID, that a licensing system can use to tell devices apart.

Where it comes from

System Source Notes
macOS IOPlatformUUID, a property of the platform device in the I/O Kit registry Apple’s header describes it as the machine’s UUID as a string. The same value shows as Hardware UUID.
Linux /etc/machine-id 32 lowercase hex characters, set at install or first boot. It does not change when hardware is replaced.
Windows A machine GUID the registry holds Written at installation. Libraries such as node-machine-id read it.

On a Mac you can read the macOS value from a terminal:

ioreg -rd1 -c IOPlatformExpertDevice | grep IOPlatformUUID

What goes wrong

  • Cloned disks and images. The Linux manual says images used on several machines should ship with the file empty or missing, so each machine generates its own. Images that skip this give many machines one id.
  • Reinstalls. A new operating system installation usually creates a new id, so a customer who reinstalls looks like a new device.
  • Editing. The node-machine-id README notes that an administrator on Windows, or root on Linux, can change the value. A hardware id is a hint, not proof.
  • Virtual machines. A copied virtual machine carries its ids along.
  • No portable source. There is no single cross-platform id. The Python guide in the repo sends none for this reason.

Privacy

The Linux manual says the machine ID should be considered confidential, must not be exposed in untrusted environments such as the network, and should be hashed with a keyed hash and an application-specific key rather than used directly. The same advice suits every platform. If you send the raw value, any two vendors holding it can recognise the same customer’s machine.

Hardware ID versus machine fingerprint

The hardware ID is the input. A machine fingerprint is the output you send: the hardware ID, or several inputs, joined with a salt and hashed. Say “hardware ID” for the raw value on the machine, and “fingerprint” for the hash that leaves it.

How Clavem handles it

Clavem never reads a hardware id. Your app does, and sends a hash as the optional fingerprint field on activation, up to 200 characters. The docs say to send a hash, not a raw id. The repo’s Swift guide hashes the Mac’s IOPlatformUUID. The Electron guide uses node-machine-id, which already returns a SHA-256 hash by default. The Rust guide suggests the machine-uid crate, and Python has no portable source, so you add one yourself if you need it.

The pitfalls, including what to do when the hash changes, are in machine fingerprinting pitfalls. The call is in the API reference.

Questions

Is a hardware ID the same as a serial number?

Not necessarily. A serial number is printed by the manufacturer. The ids used for licensing are usually UUIDs or GUIDs that the firmware or operating system installer creates.

Can I send the hardware ID to the license server as it is?

Do not. Hash it with a salt that is specific to your product first. The raw value identifies the machine to anyone who sees it.

Sources

  1. freedesktop.org, machine-id(5) manual page (checked November 2026)
  2. Apple XNU source, IOKitKeys.h, kIOPlatformUUIDKey (checked November 2026)
  3. node-machine-id README, how the id is chosen per operating system (checked November 2026)