BlackDex ca1a9e26d8

Remove SET CONSTRAINTS during postgres migration ...

The PostgreSQL migrations do not need this setting.
I tested this by running an old Vaultwarden instance (v1.18.0) on a new
PostrgreSQL database, created a few users and some vault items, after
that run the new code and it doesn't break.

Fixes #3930

2023-10-09 20:55:09 +02:00

..

api

our selves -> ourselves

2023-10-07 22:07:38 +03:00

db

Remove SET CONSTRAINTS during postgres migration

2023-10-09 20:55:09 +02:00

static

Update admin interface

2023-08-31 21:14:53 +02:00

auth.rs

Allow Authorization header for Web Sockets

2023-08-31 12:35:20 +02:00

config.rs

Fix typos

2023-10-05 20:08:26 +03:00

crypto.rs

Remove get_random_64()

2022-11-13 10:03:06 +01:00

error.rs

Cleanups and Fixes for Emergency Access

2022-12-04 23:17:48 +01:00

mail.rs

Change String to &str for all Rocket functions

2023-04-30 17:18:12 +02:00

main.rs

filter handlebars logs

2023-10-07 16:24:21 +02:00

ratelimit.rs

Basic ratelimit for user login (including 2FA) and admin login

2021-12-22 21:48:49 +01:00

util.rs

Do not send extra headers for Upgrade connection

2023-10-09 20:11:20 +02:00