What specifically is terrible?
SSO, then password manager.
I'd strongly recommend bitwarden, having deployed and managed it. I would warn against lastpass, strongly, due to papercut level issues everywhere. I haven't used 1password in an appropriate scenario to comment on it.
>+A +B
It is annoying but it works.
Do you mean the browser extension search feature?
Thanks for pointing it out.
I never touched Bitwarden project but I hope I or someone could contribute to a better search in the extension.
And you get all the excellent Bitwarden apps and extensions to go with it.
Sure I'd prefer a Linux Proton Drive client over a BTC wallet, but nobody's perfect.
Proton will pwn you if Interpol smiles at them the right way. This is common knowledge.
Why are you saying this? To justify your own use of free big tech services at the cost of all your data? Proton services have been audited, Proton staff cannot access your encrypted data. Whereas we know from Snowden et al that your data in most public clouds is readily available to the world police. Make a pic of your kid's private parts for medical reasons and people have found out the difference. My pictures are encrypt before they go to Proton Drive.
If Apple starts on-device scanning to see if I'm a criminal while I sleep, I'll be on GrapheneOS several days later, but still a happy Proton user.
Don't use any external service hosted in a country that complies with LEO or MLAT requests from the country of your residence. Actively seek out services hosted in countries that are hostile to the country of your residence.
Host your own infra, with your own authenticated FDE, reed switches and shock sensors for instant power-down on the cabinet, tamper-resistant and tamper-evident everything. Tor Hidden Services and i2p eepsites for any and all private correspondence if you really take this seriously.
We ended up using Dashlane because its free tier allows sharing between users but the administration is so much more work than it needs to be.
It’s a really weird edge case but eye opening for me as someone who is usually in a very well resourced tech environment. Google offers a great free tier for non profits and in the ideal world we’d have a password manager that plugs into our Google organization without a second thought. But that’s a premium tier feature and any money not spent on enriching the kids education has to be justified to the nth degree. We have people who are go-tos for a two factor auth code because their phone numbers are the ones attached to the accounts… people will go to surprising lengths!
There isn’t a good business case for it as such but volunteer organizations (as opposed to well resourced non profits) would make good use of a free tier and it would generate goodwill with people who are sometimes responsible for purchasing decisions in their day jobs.
It has SSO / encryption / self hosting / ... and even the enterprise version is free for up to 10 users and if you need more you only pay €2.5 / user / month.
It seems to work well / just works.
There was the time they lost customer data in a hack and then lots of customers data was exploited. https://en.m.wikipedia.org/wiki/LastPass
Many sites have forgotten password flows, they’re easy, but many other sites related to municipal services, etc, require hours on calls, often on hold, proving my identity and getting access reinstated.
Just no.
Nobody with the goal of security should be using LastPass. Nobody.
For example here some issues I flagged to the team. Note that some of them may possibly have been resolved since then:
– The “incorrect ciphers” error that keeps happening where you have to restart Bitwarden and lose all your changes.
– Basic searches take multiple seconds if you have more than 400 entries.
– Editing items is awkward. Whenever I scroll down an item and want to edit a specific entry, I have to find the edit button and then WOOSH a new panel appears and I don’t know where the field I wanted to edit ended up in the new panel.
– Bitwarden doesn’t automatically categorize login items by type and it's not possible to exclude items from the “All Items” list. So it's a big mess and when you try to search a massive amount of irrelevant auto-generated entries pop up.
– Scrolling is super laggy on Android.
– Android logins don't have icons (they could very easily extract them when Bitwarden automatically creates an entry when logging on an Android app).
– Phone numbers are not formatted. Same for many other data types.
– Credit/debit cards show a generic icon rather than Mastercard, Visa, American Express, etc.
– The whole interface is marked as selectable in CSS and when you try to move the window around it keeps selecting irrelevant text from the UI such as “Search Vault” and “Item Information” instead of moving the window. Likewise, if I try to select actual text the selection isn't constrained to the field I'm selecting from so I often select a bunch of crap I didn't mean to select.
– Clicking on a password field doesn't offer the option to generate a password.
– Password generation settings don't synchronize between Bitwarden instances. Every time you install the app or the browser extension you have to reconfigure the length, symbols, letters, casing, etc. Again. By default it uses Bitwarden's default basic (and pretty insecure) criteria.
– Bitwarden frequently doesn't detect password fields, and frequently doesn't offer to automatically save the password.
– Can’t drag & drop an item from the list to a folder. I have to manually edit the item entry and select the folder from the dropdown. Every time.
– When editing an item, the ‶Attachments″ entry is a tiny line hidden below ‶Master password re-prompt″ so it's incredibly easy to miss and hard to find.
– Attachments don’t have previews and you can't rename them. You have to manually download a given item and open it in order to see what it's about.
– Can't copy attached images to the clipboard. Instead you have to press the download button, pick a folder, find it, copy the file (or possibly open it with an image editor when you need to copy the image itself), and then paste it where you want.
– Automatic entry names are dumb. For example for Android apps it just picks the package name (e.g. com.voyagerx.scanner) instead of the name of the app (in this example the corresponding app's name is vFlat, so not clear from the package name!).
And this is only the tip of the iceberg. I had many more issues than those with Bitwarden. None of these issues happen on 1Password.
In my experience (as in IC), the real issue is when the company don’t want to pay enough seats for everyone.
Honestly sometimes it makes sense when you don’t use the tool everyday but it’s a PITA.
I think, maybe, that SaaS companies should reflect on a (capped) per-day billing for those accounts.
Some services require shared passwords, keys, or tokens. Consider grouping them by sensitivity. Key to the kingdom shared accounts should be accessible only to a tiny number of people.
Finally, never send credentials over plaintext, such as email or Slack. 1Password and other password managers have a “share” feature. If need be, send a zipped and encrypted text file and share the password via a voice call.
Because people are lazy and not everyone wants to write a file, zip it, encrypt it, call someone, spell the password... Consider sending the password regularly over slack, wait a minute till the other side confirms they got it, and remove the message.
Mediocre solutions that people use are better than perfect solutions that everyone circumvents.
Slack works for us in a very small (<5) number of trusted long-time remote devs, but with two important conditions:
1. New/updated password(s) to be shared are in an encrypted Keypass file (encrypted with a preset and prearranged password that was only shared once offline). Recipient merges into their local keypass file.
2. Confirm recipient is online, send, confirm receipt, delete immediately afterwords.
We use many AWS services so obv all those are handled with AWS Secrets and IAM, so we only need to save the login pwd externally. And for services which support multi-user, Google, GitHub, etc., each user has their own pwd. So not many passwords need to be shared in the above manner. In daily use I keep KeyPass open and copy/paste passwords into the browser when needed -- nothing stored online.
The SSO tax is real though, especially if you're a < 50 person entity and don't need everything else that normally comes with "Enterprise" plans <sigh>. Shout out to the few enlightened/kind SaaS peeps that don't do this (e.g. Windmill.dev) !
Remember, as you give people access to passwords, that those passwords will need to be rotated when those people change to incompatible roles or depart the company. If passwords aren't a total pain in the ass for you, you're probably doing something wrong.