I'm wondering why their enterprise clients are ok with this though. I would have thought they'd get more pressure from them since most businesses would not want to lose all their attachments if there's a problem.
Splunk licenses (and likely a ton of other enterprise-y software) are actual files, so when we renew our license, it goes into 1P as an attachment on our Splunk item
I recognize that's not what you would use attachments for, but I'm offering that there are enterprises that get benefit from attachments, not just individual users
We have Software Asset management tools that manage those assests, This also tracks renewal dates, and various other aspects of Software management that makes password managers not a good fit.
Our password manager is just a password manager, I suspect many other organizations are the same.
I only noticed attachments exist after this post. They are pretty hidden away and there are other ways to store SSH keys that do get included in the export.
Or maybe businesses forbid attachments in the first place or maybe they haven't realized and are okay with what being now locked in the service.
Isn't the bitwarden client opensource enough or the implementation free that someone could come in and modify the export functionality or add the functionality to the API ?