What changed, and why it matters
This commit only updates the README.md file to document memory safety settings that were already present in the release builds. It does not change any code, configuration, or actual security behavior of the app. It is a documentation-only change explaining that strict native memory checks are enabled for Android and iOS/macOS builds.
No action required. This is a documentation-only commit. If reviewing the actual security posture, verify the described settings in AndroidManifest.xml and entitlements files match the documentation, but this commit itself introduces no risk.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds a ‘Memory safety settings’ section to README.md describing existing platform-level native memory protections: Android MTE sync mode, GWP-ASan, zeroed heap allocations; iOS/macOS hardened process/heap and Memory Integrity Enforcement. No source code, manifest, entitlement, or build configuration files are modified. The commit is purely informational.
Changed components
README.mdInspect captured patch +19 / −0
### README.md
@@ -144,6 +144,25 @@ flutter run -d <device_id>
Make sure you have an Android emulator running or a physical device connected before running the app.
+### Memory safety settings
+
+The release builds turn on the platforms' strictest native-memory checks, for
+the C and C++ in the app (the Flutter engine, Monero, Tor, FHSE):
+
+- **Android** (`android/app/src/main/AndroidManifest.xml`): Arm MTE in sync
+ mode (Pixel 8 and later, when MTE is on), GWP-ASan on every launch, and
+ zeroed heap allocations.
+- **iOS and macOS** (`Runner.entitlements`, `Release.entitlements`): the
+ hardened process with a hardened heap, and Memory Integrity Enforcement
+ (hardware memory tagging on A19 iPhones and M5 Macs) enforced rather than
+ in soft mode.
+
+These stop a use-after-free or overflow at the faulting access. The cost is
+that a latent heap bug in any of that native code, harmless elsewhere, ends
+the app on that hardware, unlock included. A crash there that does not happen
+on other devices points here first: the crash report names a tag mismatch or
+GWP-ASan.
+
## Building for Android
### Debug APKWhy this scored 12/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.