Our Remedy to this issue is to permit updates into the support code at any place, assuming that the update is built transparent initial (as stated in our new CACM posting) by introducing it to some tamper-proof, verifiable transparency ledger. This provides two critical Attributes: first, all consumers of the assistance are served the identical cod