Viewing profile — dkatsura

[flagged]

[flagged]

[flagged]

[flagged]

[flagged]

[flagged]

Most private messaging advice says: use a secure messenger. That makes sense for transport and server-side privacy, but every mobile message exists somewhere before it reaches the …

Maker here. If you think this is security theater, please don’t be polite — pick one and attack it: 1. “policy travels with ciphertext” — why is that a bad idea vs external workflo…

Maker here — adding a concrete detail to make critique easier. Capsule = one file: header (version, KDF/AEAD ids) + encrypted payload chunks + policy tree (AND/OR over time/geo/pas…

Maker here. Quick challenge for the skeptics: Assume the capsule file leaks (someone forwards/copies it). In your view, does embedding the access policy (time/geo/password/visual k…

I built TrueLock for “secure messaging without a messenger”. Instead of sending plaintext in chat, you wrap a message (and attachments) into a single encrypted capsule file (.cfcap…

Design question: for Windows geo I chose a phone relay (QR challenge/proof) instead of trusting desktop location APIs. Is that the right tradeoff in your view, or would you prefer …

As promised, here’s a minimal sketch. *Capsule format (high-level)* * magic + version * crypto suite id (AEAD) * KDF id + parameters (for password path) * salt / nonces * policy se…

If useful, I can post a minimal capsule format sketch (header + policy fields) and a compact threat-model table (what it protects vs. what it does not).

Maker here. I’m especially interested in criticism of the threat model. If you try it, I’d love feedback on: which rule is actually useful in practice (time/geo/visual key) what is…

I built TrueLock to share content that opens only under rules, without cloud dependency or a central service. A capsule is one .cfcaps file containing encrypted payload + an embedd…