From 4429f0ed60456f7eee654898e6d45853f5ae9283 Mon Sep 17 00:00:00 2001 From: Enginex0 Date: Fri, 26 Jun 2026 16:57:12 +0100 Subject: [PATCH] docs(soter): initSigh resultCode is load-bearing The probe's signSessionOk requires resultCode==0 (SoterCapabilityProbe .kt:107), so writeInt(SOTER_OK) for initSigh is not optional. Cite the probe line in the comment so a future cleanup does not drop it on the false "detector ignores resultCode" belief, true only for the export path. --- .../TEESimulator/interception/soter/SoterServiceInterceptor.kt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/src/main/java/org/matrix/TEESimulator/interception/soter/SoterServiceInterceptor.kt b/app/src/main/java/org/matrix/TEESimulator/interception/soter/SoterServiceInterceptor.kt index 0c4227c..129c562 100644 --- a/app/src/main/java/org/matrix/TEESimulator/interception/soter/SoterServiceInterceptor.kt +++ b/app/src/main/java/org/matrix/TEESimulator/interception/soter/SoterServiceInterceptor.kt @@ -168,7 +168,7 @@ object SoterServiceInterceptor : BinderInterceptor() { forgedReply(callingUid, txId, method) { writeInt(1) writeLong(1L) // session — any non-zero satisfies the probe - writeInt(SOTER_OK) // resultCode + writeInt(SOTER_OK) // resultCode — probe requires == 0 (SoterCapabilityProbe.kt:107) } TX_FINISH_SIGN -> forgedReply(callingUid, txId, method) {