This is a Bitwarden server API implementation written in Rust
compatible with upstream Bitwarden clients*,
perfect for self-hosted deployment
where running the official resource-heavy service might not be ideal.
===> The following configuration options are available for vaultwarden-1.37.4_1:
S3=off: S3 storage backend support (experimental)
WEBVAULT=on: Vaultwarden web (bw_web_builds)
====> Database support: you have to choose at least one of them
MYSQL=on: MySQL database support
PGSQL=on: PostgreSQL database support
SQLITE=on: SQLite database support
===> Use 'make config' to modify these settings
all: drop support for FreeBSD 13, mips and risc64sf
Reviewed by: many (*)
Differential Revision: https://reviews.freebsd.org/D55624
Differential Revision: https://reviews.freebsd.org/D55642 (merged in from bofh)
many (*)
acm arrowd brooks cmt dch decke dinoex eduardo fluffy fuz gahr garga
jbeich joerg jrm kai kenrap martymac matthew mfechner michaelo mizhka
nobutaka pkubaj se tagattie thj
Anton Saietskii
GenericRikka
Gert Doering
Jan Bramkamp
Oleh Hushchenkov
Oleksandr Kryvulia
Ralf van der Enden
Yamagi
desktop kde python tcltk office
security/vaultwarden: Security update to 1.35.4
While there add BROKEN_FreeBSD_13 since vaultwarden needs newer openssl.
PR: 293400
Reported by: Bernard Spil
security/vaultwarden: fix bad patch
When a patch live in the files/ in the form of patch-<name> it is
automatically applied with -p0. a patch in the git form requires a -p1
fix the patch to be applicable with -p0
PR: 284239
Reported by: freebsd@rail.eu.org
security/vaultwarden: Security update to 1.32.5
This release further fixed some CVE Reports reported
by a third party security auditor and we recommend everybody to update
to the latest version as soon as possible.
The contents of these reports will be disclosed publicly in the future.
PR: 282795
Reported by: Bernard Spil
*/*: remove STRIP_CMD calls in rust based ports
This is not needed after bc4fedc1fec0d359365c04d43be9e32bf101a50e
PR: 246993
Differential Revision: https://reviews.freebsd.org/D46503
security/vaultwarden: fix packaging
The ownership can and should only be done in the plist never directly
in the make targets, make package should be executable as a regular user
and this is the case in the cluster)
PR: 276998
Reported by: freebsd@rail.eu.org
security/vaultwarden: Update to 1.30.3
While there address PR:276739 by installing the static configfile sample
to etc/rc.conf.d/vaultwarden.sample since www/vaultwarden/data/config.json
is for dynamic changes via the UI.
PR: 276745, 276739
security/vaultwarden: Make package rootdir friendly
- Use @dir with ownership instead of executing chown in postexec
We should never chown -R the data directory at install (because it's empty)
or when we upgrade (not needed)
- Fix the shipped configuration file, do not install it in etc/rc.conf.d,
install
it where vaultwarden will actually load it and use @sample
Differential Revision: https://reviews.freebsd.org/D41602
security/vaultwarden: Try to fix "failes to build with synth"
RUN_DEPENDS should depend on a file not a directory.
PR: 270974
Reported by: Matthias Pfaller
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
rust: bring back update to 1.63
Revert back the revert of the update of rust and related commits
This revert was drive by beside validation by portmgr via exp-run
and not respectful of the etiquette we have between committers
This reverts commit 8ecb1f8141144c1603eb4026122d2e60eeaccd64.
This reverts commit 04d257baa182926cff158f32cf459e560426add0.
This reverts commit 2757c63bd0e6d01f9f0657fe03bb3a7b49adcae2.
This reverts commit 75f4713de5e3fbd1c6a0cb572e08121814a4072e.
This reverts commit e88e592111c86fdd1c0ac8717dbef9342e15e27c.
This reverts commit 783c056d7d681d66e2c5c59251c275d65274028e.
With hat: portmgr
