Earlier quoted context omitted.
If the code is stable, why does it require maintenance at all? I dont think the amount of commits in last 6 months should even be a metric. Issues would be a better place to look for maintenance.
There are multiple issues from over 5 months ago that have no response https://github.com/keydotcat/keycatd/issues
Show HN: Keycat – A self-hosted end-to-end encrypted password manager
21–26 of 26 posts
Re: Show HN: Keycat – A self-hosted end-to-end encrypted password manager
#22Re: Show HN: Keycat – A self-hosted end-to-end encrypted password manager
#23Re: Show HN: Keycat – A self-hosted end-to-end encrypted password manager
#24Earlier quoted context omitted.
I think self-hosting, or using a regular account with BitWarden is the way to go. I just don't think E2E encryption is strong, unless implemented carefully?
I think self-hosting is risky. I trust bitwarden to fix, deploy, remedy, and investigate security fixes better than I can do :)
Re: Show HN: Keycat – A self-hosted end-to-end encrypted password manager
#25Once I created the similar solution for my own needs, and now I'm successfully using it for around 4 years: https://github.com/xonixx/gae-pass-manager Obviously it's much less powerful compared to LastPass and similar services but works for me well, allowing to securely access my passwords from any location and device.
Re: Show HN: Keycat – A self-hosted end-to-end encrypted password manager
#26Once I created the similar solution for my own needs, and now I'm successfully using it for around 4 years: https://github.com/xonixx/gae-pass-manager Obviously it's much less powerful compared to LastPass and similar services but works for me well, allowing to securely access my passwords from any location and device.
Do you have browser extension/ mobile app? How do you use it conveniently?