-
bitwarden
Discontinued Bitwarden client applications (web, browser extension, desktop, and cli) [Moved to: https://github.com/bitwarden/clients]
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
> I've personally never seen in my (for now short) career anything else than Keepass.
KeePass (https://keepass.info/) is excellent for personal usage or for infrequently changing credentials, which is why i've also had a good run with it!
That said, for something a bit more centralized and more easily manageable, i've seen solutions like TeamPass be used: https://teampass.net/
Well, TeamPass in particular has a pretty horrible UI (not respecting what i click with my mouse and janky dragging of items around, as well as weird display rules), but in general i feel like many companies out there might want a web app of sorts, even if only available in the internal network and self hosted.
Oh my, thanks for that link, I hadn't noticed. It's disappointed that addressing this[0] took 5 years and a whole lot of denying it's their fault, and that it is Mozilla's fault[1]! All it took was Chrome introducing a deadline...
[0] https://github.com/bitwarden/browser/pull/2121/commits/9d81b...
[1] https://github.com/bitwarden/browser/issues/136#issuecomment...
You can find the setup with Traefik here: https://github.com/dani-garcia/vaultwarden/wiki/Proxy-exampl...
Now - I used traefik and caddy extensively (and everything I do is in docker these days) and caddy is so much, much better than traefik.
I used traefik v1 and v2 and struggled with having an optimal configuration. With caddy it just works.
The main difference is that with traefik you usually try to squeeze your configuration in the docker-compose.yaml, but end up with a traefik configuration as well.
With caddy you have everything in a caddy file - in my case adding a service with plenty of things set up (filtering for networks etc. is a matter of adding
https://my-new-service.com {
Though it looks and sounds good, how would security be impacted by using the google chrome-based electron runtime to run the desktop client’s TypeScript and CLI runtime to run the server’s C# code? Wouldn’t this increase potential attack surface and probability of introducing vulnerabilities through more complexity (though this could be said for writing more of the stack oneself)? Im thinking about pass (https://www.passwordstore.org/) and KeePass 1.x (https://keepass.info) for comparison.