> You'd need a reliable way to store the state to avoid tampering. It's the same problem. If the user can set it, then it can also be set by malware running at

> You'd need a reliable way to store the state to avoid tampering. It's the same problem. If the user can set it, then it can also be set by malware running at the same privilege as the user. The only solution is to move the check outside of this privilege level (i.e. the readonly `.text` section of the firefox binary in /usr/ or Program Files). That's what the signing requirement does.