ab4fe643a3
Apps attempting to update the certificate chain of a simulated software-based key (e.g., via KeyStore.setKeyEntry) currently trigger a KEY_NOT_FOUND error. This happens because the request is passed to the hardware Keystore daemon, which has no knowledge of keys existing only in the simulator's memory. To fix detecting points exploiting this inconsistency, we intercept the UPDATE_SUBCOMPONENT_TRANSACTION. If the target is a recognized virtual key, the simulator now: 1. Updates the in-memory certificate/chain metadata. 2. Returns NO_ERROR immediately to the caller. 3. Prevents the transaction from reaching the real hardware service. Co-authored-by: JingMatrix <jingmatrix@gmail.com>