- 10 Posts
- 15 Comments
wardcore@lemmy.worldOPto
Privacy@lemmy.world•Emergency PIN with a full decoy environment - ONYX v1.5-betaEnglish
1·6 months agoYeah, you’re right. I’ll fix this in the next update.
wardcore@lemmy.worldOPto
Privacy@lemmy.world•Emergency PIN with a full decoy environment - ONYX v1.5-betaEnglish
2·6 months agoOn mobile the key comes from the platform keychain — tied to device unlock, not the app. On desktop it’s machine-derived. The decoy PIN threat model is coercion — someone watching you unlock. If an attacker already has filesystem access, you’ve got bigger problems than the PIN.
wardcore@lemmy.worldOPto
Privacy@lemmy.world•Emergency PIN with a full decoy environment - ONYX v1.5-betaEnglish
1·6 months agoNo, it’s not one file with two decryption keys — you’ve got the architecture slightly wrong. There’s one storage, encrypted with AES-256-GCM. The PIN doesn’t decrypt the file — it’s verified at the application level. If the real PIN matches, the real environment loads. If the decoy PIN matches, the decoy environment loads with its own data, stored in the same storage under separate keys. Two layers of data in one container, not two containers with different keys.
wardcore@lemmy.worldOPto
Privacy@lemmy.world•Emergency PIN with a full decoy environment - ONYX v1.5-betaEnglish
51·6 months agoGood points, but the architecture is a bit different. It’s not two separate encrypted files — from the outside there’s no indication there are two PINs at all. The decoy environment looks like a fully functional account: its own chats, groups, contacts, message history. The attacker doesn’t know there’s a second layer because nothing tells them the first layer is a decoy.
Your approach of generating a random DB for any wrong PIN is interesting too, but it has a different problem: there’s no “correct” result, any PIN “works”, and a paranoid attacker can figure that out. Here the decoy environment is convincing precisely because it’s a real-looking account, not a placeholder.
On encryption: AES-256-GCM, keys derived via HKDF-SHA256 with salt. The code is fully open source on GitHub — that is the documentation. Separate security docs don’t make sense for me to write right now, but if the project grows — definitely yes.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX v1.4-beta: voice channels for LAN parties and a media player that actually looks goodEnglish
5·7 months agoThis update actually wouldn’t have happened without your suggestion — you pushed me to finally implement it. Thank you!
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX 1.3-beta — reactions, blocking, and notification privacyEnglish
3·7 months agoMessages are stored on the server only until the recipient comes online. Once they connect, a 30-second timer starts — after that the message is permanently deleted from the server. There’s no copy left server-side after that point. Since private chats use E2EE, the server only ever sees ciphertext anyway. After delivery, messages exist only locally on both devices. If you want no local record either, you can delete the conversation manually from within the app.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
3·8 months agoWrite to @support directly in ONYX, using the search field, and we’ll discuss this in detail.

wardcore@lemmy.worldOPto
Privacy@lemmy.world•I tried to build a messenger that doesn't make you choose between privacy and convenience.English
51·8 months agoHonestly, the main motivation was just curiosity - I wanted to see if I could build something like this, and then put it out there to see if anyone actually cares.
wardcore@lemmy.worldOPto
Privacy@lemmy.world•I tried to build a messenger that doesn't make you choose between privacy and convenience.English
31·8 months agoFair point, I just missed adding it to .gitignore.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
42·8 months agothat’s a great idea, I’ll consider adding it in one of the upcoming updates.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
99·8 months agoFair skepticism, but no - I used AI for the English translation of my post, since I’m not a native speaker.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
23·8 months agoJust to clarify — E2EE in ONYX is only for private chats. Groups and channels (both built-in and self-hosted) don’t have E2EE, which is actually closer to your point — for groups it’s a deliberate tradeoff for simplicity and reliable sync. So you’re right, for that use case TLS is enough.
wardcore@lemmy.worldOPto
Selfhosted@lemmy.world•ONYX: self-hosted messenger with LAN mode and E2EE — an indie project storyEnglish
317·8 months agoFair point! Yes, Claude was used as a coding assistant throughout the project. That said, every single line went through strict manual review — nothing was blindly copy-pasted into the codebase. All architectural decisions, the crypto stack choices, and the overall design are my own. Claude helped with boilerplate and speeding things up, but the project is not “vibe-coded”.


The people actually shipping slop hide the AI usage - I don’t. Make of that what you will.