12189dcd75
Verify inbound nostr signatures (C1): NostrEvent.fromEvent now calls quartz Event.verify() (id-hash integrity + Schnorr) and drops the event on failure. fromEvent is the single inbound parse choke point, so forged events from a malicious/compromised relay can no longer reach the DB (profile overwrites, fake notes/reactions, etc.). Persist + retain PrivateMessage commits (H2): applyCommit's PRIVATE_MESSAGE branch captured no epoch secrets and never persisted the advance, so decrypt()'s inline commit was lost on reload and prior-epoch messages became undecryptable. Capture retainedSecrets before decrypt and pushRetainedEpoch + persistGroup on a successful advance, matching decryptMessageBytes/processCommit. Fix membership/admin reconciliation inversions (H3/M1/M2) in processGroupMembershipChanges: new-member filter now negates correctly so new joiners are persisted; the new-member admin flag uses == true instead of == null (previously marked everyone admin when adminPubkeys was absent, nobody when present); removedAdmins uses != true so admins actually dropped from the list are demoted instead of stripping current admins. Document retained-epoch impersonation (C2) and plaintext-at-rest (H1): these can't be fixed in-app (RetainedEpochSecrets carries no tree/leaf sig keys/groupContext to verify a past-epoch signature; encryption-at-rest needs a platform keystore). Add prominent SECURITY warnings/TODOs at tryDecryptWithRetainedEpoch, the ncryptsec* key-package fields, and the mlsGroupState persistence, with the required fix in each case. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This is a Kotlin Multiplatform project targeting Android, iOS, Desktop (JVM).
-
/composeApp is for code that will be shared across your Compose Multiplatform applications. It contains several subfolders:
- commonMain is for code that’s common for all targets.
- Other folders are for Kotlin code that will be compiled for only the platform indicated in the folder name. For example, if you want to use Apple’s CoreCrypto for the iOS part of your Kotlin app, the iosMain folder would be the right place for such calls. Similarly, if you want to edit the Desktop (JVM) specific part, the jvmMain folder is the appropriate location.
-
/iosApp contains iOS applications. Even if you’re sharing your UI with Compose Multiplatform, you need this entry point for your iOS app. This is also where you should add SwiftUI code for your project.
Build and Run Android Application
To build and run the development version of the Android app, use the run configuration from the run widget in your IDE’s toolbar or build it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:assembleDebug - on Windows
.\gradlew.bat :composeApp:assembleDebug
Build and Run Desktop (JVM) Application
To build and run the development version of the desktop app, use the run configuration from the run widget in your IDE’s toolbar or run it directly from the terminal:
- on macOS/Linux
./gradlew :composeApp:run - on Windows
.\gradlew.bat :composeApp:run
Build and Run iOS Application
To build and run the development version of the iOS app, use the run configuration from the run widget in your IDE’s toolbar or open the /iosApp directory in Xcode and run it from there.
Learn more about Kotlin Multiplatform…