3
Support the phishing-detection experimental client flag
Source: dani-garcia/vaultwarden#7036 · opened by @zu3st
Bitwarden recently integrated a [Phishing Blocker]( feature into its browser extension, warning users when visiting sites listed in the open-source [Phishing.Database]( No Vaultwarden-specific server support is needed beyond exposing the experimental client feature flag phishing-detection. However, since Vaultwarden limits configurable client feature flags to a set hardcoded in [config.rs]( the feature currently cannot be enabled without a custom build. This can be verified by adding phishing-detection to the accepted flag list, starting Vaultwarden with EXPERIMENTAL_CLIENT_FEATURE_FLAGS=phishing-detection, setting up the extension against that instance, and then visiting With that in place, the extension shows the phishing warning as expected. Since this is already an upstream experimental client flag, adding it to Vaultwarden’s allowlist seems like a low-risk improvement that would let self-hosted users opt in without requiring any long-term stability guarantees. <im…
No pledges yet. Be the first to back this.
Comments
Similar requests
Why do we not allow arbitrary client side feature sets?
3 votes · 0 comments
Enable feature flag "PM-4154-multi-worker-encryption-service"
1 vote · 0 comments
Feature Flags accessible via Admin Console
3 votes · 0 comments
Multiple Servers / External Users
2 votes · 0 comments
Move SSO_CLIENT_SECRET to the Read Only Admin Panel or Encrypt it
1 vote · 0 comments
No comments yet.