Recently, bitwarden has been asking me every time whether it should save the password, even though I’ve clicked never on this password a thousand times
Windows 11: current, Chrome: current, BitwardenVersion: 2024.11.2
Go to Settings > Notifications > Excluded Domains and confirm that the domain in question is listed there (if not, add it manually).
I’ve already done that and nothing has changed
So, the domain was already there when you checked, or it disappears after you add it?
all excluded domains are displayed, but have no effect
I also uninstalled the bitwarden addon and reinstalled it but no effect on excluded domains
I am still asked if I want to save the password even for excluded domains
Hi, I’ve got similar problem with Bitwarden 2024.11.0 not observing excluded domains list.
While BW exclude domain list seems to work as intended in my Mozilla Firefox 133.0 (64-bit), unfortunately in Avast Secure Browser Version 130.0.27176.93 (Official Build) (64-bit) keeps asking for saving logins and passwords despite my numerous answers to “Never” do it (no need to mention, visiting the very same excluded domains). To my knowledge Avast Secure Browser presents itself as Chrome in some situations, so perhaps the problem is limited to Chrome (or in general, dependant on the browser make being used).
Or - maybe - it is the problem of the recent BW update/upgrade…
Checking “About BW” used with my Firefox reports Bitwarden Version 2024.11.0 and Server Version Version 2024.11.0, while with Avast Secure Browser reveals Bitwarden Version 2024.11.2 (!) and Server Vesion 2024.11.0.
Since the older BW version (the one on my FF) works OK, I am very reluctant to even try to refresh it to the newer one
I am very much interested in your thoughts and ideas how to possibly rectify the situation on ASB. Is, for example, installing backdated version on ASB a possible option?
You can download dist-chrome-2024.11.0.zip
from GitHub, but I don’t know if ASB allows sideloading of extensions that are not obtained directly from the app store (or if they do allow it, what the procedure is for doing so). Some app stores also provide access to earlier versions of an extension, so you might look into that, as well.
Also, @palant (a security blogger and the original developer of Adblock Plus) has written an interesting review of security issues in the ASB browser, which you might want to read.
Many thanks for your quick response.
The way through GitHub seems not for me, as I am not versed enough to tweak all the necessary details unless instructed step by step ;). I think I will simply wait till BW developers have fixed it somehow.
On the other hand it may be not necessary (from my pov), since the link that you provided helped me to seriously consider simplification of my environment and basically stick to only one browser (FF).
BTW, reading the Vlad’s article (and other linked within) was for me like drinking from a firehose… I will need more time to get deeper/wider into this interesting info. Thanks again for sharing with me the source.
This same thing is happening for me. Linux Mint (xfce), Firefox (133.0 (64-bit)) BitWarden 2024.11.2. NOT self hosted.
It’s incredibly annoying and probably a deal breaker (back to LastPass) if I can’t get it resolved.
Looks like the problem is indeed with the recent BW update on the client side.
Today morning - to my dismay - my FF asked me if to save the password for one of my the excluded domain :-(, so I checked out and I discovered that over the weekend the BW version on my FF changed from 2024.11.0 to 2024.11.2 (unwanted auto-update - another issue?).
I’d like to have the ‘excluded domains’ problem formally reported to BW developers as a bug. I learned that it can’t be done here (BW users’ forum), but somewhere on GitHub, which I’m not familiar with. I’d appreciate some assistance in finding the right place to do so (discussion/search, post(s), form to fill, etc…). Thanks in advance for your help.
For the clients (extension, desktop app, web vault, CLI), this is the place: Issues · bitwarden/clients · GitHub (click on “New issue” - and you have to register for GitHub for that)