feat: bind each licence to the computer it was activated on #2
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/machine"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Copying
licence.jsonto another computer unlocked Pro there, so the three-machine limit only counted activations through the server.machine:machineid.ProtectedID(product), an HMAC-SHA256 of the OS machine ID keyed by the product, so the raw ID never leaves the computer and differs per product. The Worker requires it (64 hex characters) and signs it into the token; it isn't sent to Polar.VerifyandLoadreturnErrOtherMachine(with the licence) when the token names another computer; the app offers to activate there, which takes a slot.Deactivateon a copied licence only deletes the file: it doesn't free the original computer's activation.Needs a Worker deploy before apps send
machine; the old Worker would ignore it and issue tokens apps then reject.