inertia-rs
vaultwarden
Our great sponsors
| inertia-rs | vaultwarden | |
|---|---|---|
| 1 | 416 | |
| 17 | 23,774 | |
| - | - | |
| 0.0 | 8.3 | |
| about 1 year ago | 5 days ago | |
| Rust | Rust | |
| - | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
inertia-rs
We haven't tracked posts mentioning inertia-rs yet.
Tracking mentions began in Dec 2020.
vaultwarden
- Self Hosted Bitwarden Docker Compose
-
How do you folks make it so you remember all the passwords to all the systems and services you run?
There are some good solutions here in the vaultwarden wiki, I was considering implemented the one that pushes an encrypted backup to a cloud storage provider. https://github.com/dani-garcia/vaultwarden/wiki/Backing-up-your-vault
-
Does LastPass really deserve a last chance?
Trying Bitwarden, but I may give https://github.com/dani-garcia/vaultwarden a chance as well
-
Trying to get vaultwarden working locally
You can enable HTTPS on the vaultwarden container itself https://github.com/dani-garcia/vaultwarden/wiki/Enabling-HTTPS using the ROCKET_TLS environment variable and publishing port 443 of the host to port 80 of the container.
-
Password manager for lan
Well you can create companies/organisation. I haven't looked into this yet. Maybe look on there GitHub or other vaultwarden wiki https://github.com/dani-garcia/vaultwarden/wiki
-
Self hosted PW manager
Vaultwarden is an open version of bitwarden. Works the same, official bitwarden clients do work https://github.com/dani-garcia/vaultwarden/releases
-
Change Your LastPass Password Manager, Before It's Too Late
I just deleted my Lastpass account and switched to Vaultwarden (https://github.com/dani-garcia/vaultwarden) instead.
-
Re-License Vaultwarden to AGPLv3
jjlin raised some valuable points in https://github.com/dani-garcia/vaultwarden/discussions/2450#..., where the initial motivation and reasoning were faulty or incomplete:
> While I don't object to changing the license, I think a few things mentioned in the intro are not quite true and should be clarified.
> > To be clear, this will not effect any (end)user or any self-hosted environment which you share with your family and friends.
> If you make your Vaultwarden instance publicly accessible, then there is a reasonable expectation that anyone could interact with it (if only to load the login page), so if you've modified any of the Vaultwarden backend (e.g., custom templates or graphics that get built into the binary), I believe you would technically be obligated to "prominently offer" the source. In practice, that would probably mean modifying the web vault login page with a link to your source.
> > This will only have an effect on companies that build proprietary tools using Vaultwarden code.
> As mentioned above, this also affects non-commercial users who have modified the Vaultwarden code.
> > This is also more fair towards Bitwarden, since currently the GPLv3 license of Vaultwarden could allow other companies to compete with Bitwarden, which is not something we want.
> While this may prevent deep integration of Vaultwarden with a company's other products, they are still perfectly able to provide standalone instances, even with some customizations (as long as they make the modified source available), so I don't think this change would have much effect on most MSPs who offer managed Vaultwarden services.
> Overall, AGPL has a limited ability to prevent third-party competition with the original product, as can be seen with Bitwarden's shift towards a non-open-source ("source-available") license for key portions of their software.
—⁂—
Me, I’m not convinced this change is (a) desirable or (b) worthwhile, for the same reasons as jjlin, but I don’t oppose it either. As a teenager I was generally quite unimpressed by the GPL and deliberately avoided building with some copyleft things where possible, strongly favouring permissive licenses, but now I’m 30 and I’ve definitely come to appreciate the purposes of copyleft licenses a bit more, though I still largely prefer to work with permissive licenses.
(I prefer the Blue Oak Model License <https://blueoakcouncil.org/license/1.0.0>; on the licenses’ own merits, BlueOak-1.0.0 is roundly better than the likes of Apache-2.0 and MIT; the only practical imperfection of BlueOak-1.0.0 is that it’s not OSI-approved, largely because—simplifying perhaps well past the point of strict accuracy—its authors used to work with OSI and are fed up with broken processes.)
What are some alternatives?
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
Passbolt - Passbolt CE Backend, a JSON API written with Cakephp
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
keepassxc - KeePassXC is a cross-platform community-driven port of the Windows application “Keepass Password Safe”.
authelia - The Single Sign-On Multi-Factor portal for web apps
sso-wall-of-shame - A list of vendors that treat single sign-on as a luxury feature, not a core security requirement.
Nextcloud - ☁️ Nextcloud server, a safe home for all your data
web - The website vault (vault.bitwarden.com).
totp-generator - Generates TOTP tokens in the browser
bitwarden_rs - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs [Moved to: https://github.com/dani-garcia/vaultwarden]
pass-import - A pass extension for importing data from most existing password managers
yt-dlp - A youtube-dl fork with additional features and fixes