From 82490385e58ccc6e32707c0621ff15828e6616ab Mon Sep 17 00:00:00 2001 From: Viharm Date: Sat, 25 Jul 2026 16:04:35 +0100 Subject: [PATCH] =?UTF-8?q?=E2=9C=8F=EF=B8=8F=20Hardening=20guide:=20Minor?= =?UTF-8?q?=20grammatical=20typo.?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Hardening-Guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Hardening-Guide.md b/Hardening-Guide.md index 63e24bc..365e681 100644 --- a/Hardening-Guide.md +++ b/Hardening-Guide.md @@ -41,7 +41,7 @@ Example GET request: If your reverse proxy is configured to save access logs, or the access logs are shipped to an external service such as Prometheus + Promtail, it is recommended to redact the value of the `access_token` parameter on the external log store, or directly on your reverse proxy of choice, if supported. -No other data is ever send via GET request, encrypted or unencrypted. +No other data is ever sent via GET request, encrypted or unencrypted. Be advised that internal vaultwarden logging strips query to 30 chars, hence access_token is truncated, meaning if not using reverse proxy, you shall be safe from this by default.