d0mkaaa

6 ms·

1. 1.▲
   by d0mkaaa 19d ago

   Yeah I can see what you mean, but it wasn't really intentional. I mainly wanted to avoid the usual black/blue security-product look. I will probably keep the general direction but give it more of its own identity over time. Thank
2. 2.▲
   by d0mkaaa 19d ago

   I don't really have anything against the big password managers either. I just don't love having to pay for a full year upfront with some of them. More than that though, a lot of them just don't quite fit what I want, or they
3. 3.▲
   by d0mkaaa 19d ago

   Yes. Every lock entry point (manual, auto-lock timer, app shutdown) funnels through one function, so the behavior can't drift, that calls lock_for_lifecycle, which drops the unlocked session. Dropping UnlockedVault zeroizes the 32-byte
4. 4.▲
   by d0mkaaa 19d ago

   Passkeys will be added in the coming weeks
5. 5.▲
   by d0mkaaa 19d ago

   KeePassXC is definitely much more mature right now. I mean, Sesame is similar in being local-first and not requiring a cloud service, but I am aiming for a more modern consumer style experience. There is still a lot of work ahead to get it
6. 6.▲
   by d0mkaaa 19d ago

   vaultwarden + bitwarden is way more mature right now, but the main difference is that sesame is local-first by design. Vaultwarden also depends on staying compatible with bitwarden's clients/api, while this owns the whole stack
7. 7.▲
   Show HN: Sesame - a local-first, open-source password manager(usesesame.app)

   66 points by d0mkaaa 19d ago|85 comments