Under the hood
Useful2 Signal0
Config writes now report whether they actually succeeded, so a failed or compromised save isn't treated as done.
What's wrong with this entry?
Anonymous. No account, no email.
What
The locked config-write helper now tells its caller whether the write actually succeeded, which is what lets the machine id path avoid handing out an id it failed to persist.
Details
- the helper returns a boolean instead of nothing
- an
onCompromisedcallback is passed into the lock and sets a flag - a no-op write is tracked separately, so an unchanged config still counts as success while a compromised lock does not
Evidence
{ onCompromised: () => (o = !0) }
Strings lifted out of the shipped bundle, so the claim above can be checked against them.