1
Bruteforce security for 2FA
Source: dani-garcia/vaultwarden#5470 · opened by @mangoman16
Hello everyone, while trying to set up fail2ban, I noticed that it is not possible to ban wrong 2FA attempts, since there is no IP in the Accesslog and I cannot write a regex for it: This is how my config looks like: This is a cut of the access log of me trying to log in with false 2FA (email in this case): [2025-01-27 10:49:03.224][tracing::span][TRACE] parse_headers; [2025-01-27 10:49:03.224][tracing::span::active][TRACE] -> parse_headers; [2025-01-27 10:49:03.224][tracing::span::active][TRACE] <- parse_headers; [2025-01-27 10:49:03.224][tracing::span][TRACE] -- parse_headers; [2025-01-27 10:49:03.225][request][INFO] POST /identity/connect/token [2025-01-27 10:49:03.225][rocket::form::parser::_][TRACE] url-encoded field: ("scope", "api%20offline_access") [2025-01-27 10:49:03.225][rocket::form::parser::_][TRACE] url-encoded field: ("client_id", "web") [2025-01-27 10:49:03.225][rocket::form::parser::_][TRACE] …
No pledges yet. Be the first to back this.
Comments
Similar requests
Additional configuration for hardening 2FA
2 votes · 0 comments
Disable 2FA email setup button if email 2FA is disabled in admin settings
1 vote · 0 comments
2FA for web extension
2 votes · 0 comments
Default 2FA email for new users invited to organizations with 2FA-policy enabled
11 votes · 0 comments
Show notification and force if 2FA is required when first login
1 vote · 0 comments
No comments yet.