Keepassium used to be listed (I think), should I now prefer alternatives?

Privacy Questions
1

question

  • I’m reasonably certain Keepassium was previously listed somewhere on the Guides. The reason being, I hadn’t heard about it before coming across the app in recommendations and adding it to my notes. But I failed to find mention of it in Internet Archive snaps of the Password Manager page.
  • I don’t see Keepassium in recommendations now. Is there new information to factor in, when considering using this app?

context

  • Shortlisting options for my transition from Authy where I currently manage some TOTP.

  • Other TOTP also managed in a .KBDX.

  • Authy has, until now, housed those TOTP which I could use on-the-go (thus needing client on mobile), or for those services which only display QR codes during TOTP setup (not giving me a secret key which can be plugged straight into KeepassXC :roll_eyes:)

main criteria to be improved

  • make data portable: Authy data is not portable

candidates

  • Bitwarden
    • already use it
    • supports TOTP
    • reluctant to break some MFA by including TOTP alongside their passwords. Risk may be mitigated by protecting Bitwarden with hardware key.
  • Keepassium:
    • can combine TOTP from Authy into existing TOTP/recovery key storage .KBDX file
    • syncing will need infra that wouldn’t be necessary using Bitwarden.
2

FYI Recommendations can change a lot here. So, wouldn’t be surprising if it was removed.

I was able to find this discussion;

We compared Strongbox and Keepasium and decided that Strongbox offered more features both in the free and paid versions (such as not being restricted to one database).

At this point, I think Strongbox is enough, as it fits the niche that we wanted to cover (KeePass compatible app for iOS).

I can’t comment on that as I haven’t used those apps.

2 Likes
3

Yep, that discussion is the extent of what we’ve looked at with Keepassium I think.

We could look into Keepassium further if you could share specifically what you don’t like about Strongbox.

2 Likes
4

Thanks for finding and sharing this :100: I was not aware Github’s Discussions were also used as a channel by this project.

I find that, especially when few options exist which satisfy privacy and security criteria, exclusions are implied to not be trusted.

From the above discussion, I understand that options aside from Strongbox are not listed because Strongbox was deemed more feature-complete compared to alternatives on the iOS platform.

But, once a minimum privacy and security criteria is satisfied, I would prefer to choose my own user experience. I see this preference reflected in another thread about Mullvad Browser:

At this point, I’ve used neither Keepassium nor Strongbox. I have usecases and am using privacyguides.org to find trustworthy candidates that may satisfy these requirements. If Keepassium is known to be privacy-friendly, then I’ll be able to consider it a potential alternative to Strongbox Zero. Otherwise, my candidates are just Strongbox and Strongbox Zero.

5

We don’t review every app with privacy marketing, because time is a finite resource. Exclusions are weakly implied to not be trustworthy, unless you can prove it is. Inclusions are strongly implied to be trustworthy.

1 Like
6

Maybe look at it more now?
That Strongbox is not Open Source

3 Likes
7

Following the earlier conversation on this thread, I chose Strongbox. Though, I continued collecting data on KeePassium. I found more ongoing positive signals from the KeePassium developer, and eventually swapped out Strongbox for KeePassium.

Hooray for portability, folks.

8

Yeah fuctionality is pretty much the same apart from using multiple databases.
Unfortunately only one database for the free version is a huge turn down for me.

9

Sure thing.

Use cases vary, though it’s worth noting, the limitation of 1 database on free becomes less noticeable if, for example, only 1 database needs to be on the mobile device with Keepassium and the rest are fine being used only elsewhere.