KevinChasse

7 ms·

1.
Sovereign V4: A Cleaner, Stronger Approach to Cryptography(bastion-enclave.vercel.app)
2 points by KevinChasse 6mo ago|0 comments
2.
Whispered – ephemeral posts judged by the community(whispered-live.vercel.app)
1 points by KevinChasse 7mo ago|1 comments
3.
by KevinChasse 7mo ago
I built Whispered, a web experiment in ephemeral, user-driven posts. Every post is born with 120 seconds to live, and the community decides what survives: upvotes add 60 seconds, downvotes subtract 15. No post can live longer than 5 minutes
4.
by KevinChasse 7mo ago
Bastion’s cryptography isn’t AI-generated. The system follows well-established cryptographic primitives and protocols: PBKDF2-HMAC-SHA512 for deterministic password derivation, Argon2id for local key stretching, AES-256-GCM for encryption,
5.
by KevinChasse 7mo ago
Bastion isn’t designed for convenience or multi-device sync — it’s a deterministic, stateless cryptographic protocol. The master isn’t a human-memorable password; it’s a 256-bit root secret. Lowering it to a “password” breaks the threat mod
6.
by KevinChasse 7mo ago
Interesting approach. I like that this is explicit about human recovery rather than pretending crypto alone solves catastrophe. That said, this design and fully stateless systems like mine (deterministic derivation, no escrow) are solving o
7.
by KevinChasse 7mo ago
Most prior attempts reduce to hash(master || site). Bastion treats password generation as a cryptographic protocol with explicit invariants, not a convenience function. An important note is Hashing ≠ memory-hard Hashing ≠ unbiased sampling
8.
by KevinChasse 7mo ago
Rotation is explicit and deterministic via the version parameter. Old passwords can be regenerated for rollback; new ones don’t require storage.
9.
by KevinChasse 7mo ago
Bastion does not treat the master as a “password.” It is a cryptographic root secret equivalent to a 256-bit key. If you downgrade it to a human-memorable string, you are violating the security model. Argon2id + 210k PBKDF2 rounds + rejecti
10.
by KevinChasse 7mo ago
Bastion has the same failure model as a hardware wallet or SSH private key. If you want recoverability, you accept third-party trust. Bastion refuses that trade.
11.
by KevinChasse 7mo ago
Interesting approach. Exposing high-level goals rather than UI actions definitely reduces token overhead, but reproducible comparisons with open-source setups would strengthen the claim. Also, remote browsers introduce a new attack surface—
12.
by KevinChasse 7mo ago
Nice catalog. One subtle thing I’ve found in building deterministic, stateless systems is that atomic filesystem and memory operations are the only way to safely compute or persist secrets without locks. Combining rename/link/O_EX
13.
by KevinChasse 7mo ago
Nice work. One thing I've noticed with locally checking extensions against threat lists is that the verification process itself can become a target. Stateless, deterministic verification — where hashes or IDs are derived on-device and
14.
by KevinChasse 7mo ago
FYI: Bastion assumes a trusted local execution environment and a strong master secret. It does not defend against a compromised OS or browser runtime. The system trades convenience (sync, cloud recovery) for deterministic, stateless, and cr
15.
Show HN: A password system with no database, no sync, and nothing to breach(bastion-enclave.vercel.app)
14 points by KevinChasse 7mo ago|16 comments