I want to toss my thoughts into the ring, that a deb/rpm package repo really is an important thing for updating this software. For me, for a few reasons.
- It means the package manager is aware of the application, and the package manager is typically expected to manage ALL software on a common Linux system. For me, this is how I want my software to be managed wherever possible. Considering we already have deb packages, a repo is just a next step.
- My work for my employer includes working towards endpoint management in the near future, including Linux endpoints (laptops, workstations, etc) and having a repo means we can ensure updates to Bitwarden (just like other software) happen on these systems. Our Linux endpoints are scoped to be Ubuntu, and I am anticipating we will probably use landscape, hence my preference for deb/ppa repos.
- I had honestly forgotten to update my own Bitwarden client which I installed 1.5 years ago, and this actually caused bugs for me in the last few days, which seemingly were fixed by… updating manually…
This request was opened… 4 years ago? Why is this not already in-place? Automation around package distribution is a real thing, and I think it’s about high-time Bitwarden actually gets a proper repository going. For me, alternatives like flatpak don’t meet my functional needs, and that is a separate ecosystem from the core package manager I care about.
So can we just get this done already? This is a security tool, and the #1 way you address security in any regards is UPDATING. This conclusively reduces barriers for automatic updating, which meets with the security nature of this tool.