how does this compare to vaultwarden + bitwarden? my only concern there is that VW can throw self-host support out the door whenever they like. not that they'd have a reason to
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
Show HN: Sesame - a local-first, open-source password manager
21–30 of 83 posts
Re: Show HN: Sesame - a local-first, open-source password manager
#22Re: Show HN: Sesame - a local-first, open-source password manager
#23How does it compare to KeePassXC?
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 up to speed. I might also build more products around it eventually, so there’s a consistent ecosystem. (and of course, it would be great to eventually surpass some of the existing…
Re: Show HN: Sesame - a local-first, open-source password manager
#24I still don’t get why password managers builders think it’s a great idea to store MFA token together with the password, totally defeating the purpose of MFA in the first place.
(It still protects against a password leak, though, so doesn't entirely defeat the purpose of MFA.)
Re: Show HN: Sesame - a local-first, open-source password manager
#25I still don’t get why password managers builders think it’s a great idea to store MFA token together with the password, totally defeating the purpose of MFA in the first place.
Keeping the password and MFA secret in the same password manager reduces separation (if someone fully compromises your vault, they will gain access to both factors). But that doesn’t make MFA pointless; it just means it doesn’t protect you against that particular failure mode.
And if someone has full access to your password manager, you already have a much bigger problem.
Re: Show HN: Sesame - a local-first, open-source password manager
#26Earlier quoted context omitted.
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 up to speed. I might also build more products around it eventually, so there’s a consistent ecosystem. (and of course, it would be great to eventually surpass some of the existing…
What do you mean by a "consumer style experience"?
Re: Show HN: Sesame - a local-first, open-source password manager
#27Re: Show HN: Sesame - a local-first, open-source password manager
#28I like that this could be self hosted. I don't have anything against the big password managers (I use and pay for one), but they are a massive target for hackers for obvious reasons. If everyone could self host their own vault on a personal domain, the reward for hackers is much more difficult to get access to.
For now. I note that all of the repos that are attached to the project have a license except sesame-server, which I do not think is an accident.
Re: Show HN: Sesame - a local-first, open-source password manager
#29Why a whole new project that needs to re-learn the gotchas that the predecessors ran into? Could any grievances have been pull requests or, worst case, a fork?
Re: Show HN: Sesame - a local-first, open-source password manager
#30A vibe-coded password-manager? Sure! where do i sign up?