>"the properties of the object can no longer be changed" yes, unless someone else just unfreezes the object. There doesn't appear to be any unfreeze method. >

>"the properties of the object can no longer be changed" yes, unless someone else just unfreezes the object. There doesn't appear to be any unfreeze method. >This is still a problem, and the "harden" function that is described doesn't actually help because the things that it relies on could be poisoned. I think the threat model here is untrusted code which runs after the "harden" function completes. (I think this article would've been better if it had discussed threat models at the beginning.)