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.
This commit is contained in:
+1
-1
@@ -168,7 +168,7 @@ object SoterServiceInterceptor : BinderInterceptor() {
|
|||||||
forgedReply(callingUid, txId, method) {
|
forgedReply(callingUid, txId, method) {
|
||||||
writeInt(1)
|
writeInt(1)
|
||||||
writeLong(1L) // session — any non-zero satisfies the probe
|
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 ->
|
TX_FINISH_SIGN ->
|
||||||
forgedReply(callingUid, txId, method) {
|
forgedReply(callingUid, txId, method) {
|
||||||
|
|||||||
Reference in New Issue
Block a user