Andrea-lyz 4ecbfc7259 fix: use SecurityLevel.KEYSTORE in createSwAuth to match real hardware ...

Duck Detector's 'TEE Simulator generate-mode fingerprint' probe scans the
generateKey reply parcel for a 16-byte marker where the securityLevel byte
is 0x00 (SOFTWARE). Real KeyMint HAL uses 0x64 (KEYSTORE=100) for
keystore-enforced metadata (creation time, user ID, etc.).

This single-line change aligns with real hardware behavior and defeats
the probe. Tested on OnePlus 13 (Android 16, KSU 3.2.4):
- Before: 'TEE Simulator generate-mode fingerprint: Matched' (score 50)
- After:  'No TEE Simulator generate-mode fingerprint observed' (score 4)

Reference: https://github.com/eltavine/Duck-Detector-Refactoring/commit/e368038

2026-05-15 16:23:05 +02:00

..

src/main

fix: use SecurityLevel.KEYSTORE in createSwAuth to match real hardware

2026-05-15 16:23:05 +02:00

build.gradle.kts

chore(version): bump to v6.0.0

2026-03-26 12:28:23 +01:00

proguard-rules.pro

build(native-certgen): wire Rust crate into Gradle pipeline

2026-03-09 16:46:32 +01:00