[Bug] Weak Passwords banner in all items without password. [Fixed in 1Password 7.3.646 Beta 6]
Firstly, great to see the improvements that you've recently implemented.
However, I seem to have a problem with the watchtower weak passwords.
Everything other than a login item is now showing a weak password i.e. secure notes, software licences, outdoor licences etc. etc. totalling approx 100 entries.
The banners are showing in the item detail RH panel and are not counted as weak in the LH panel watchtower folder structure.
Something's amiss somewhere.
Looking forward to further improvements ….
1Password Version: 7.3.642
Extension Version: Not Provided
OS Version: Win10, v1809
Sync Type: Dropbox
Comments
-
Hi @Swivel_Eyes,
Good catch! Thanks for reporting it.
It looks like a glitch in the new viewer rather than a bug in Watchtower. We'll have this fixed in the next update.
ref: opw/opw#3662
0 -
Why am I getting "Weak Passwords" showing up on nearly all items, not just a login?
1Password Version: 7.3.642
Extension Version: Not Provided
OS Version: Windows 10 (latest)
Sync Type: 1Password0 -
Hi @mtissington,
I've merged your thread into the previous bug report on this. It's a bug that has been fixed and is coming in the next beta update.
We had a bug in the logic for the Watchtower banners where it defaulted to Weak as it didn't have a no-banner condition for non-affected items; that's why this pretty much affected almost all of your items outside of Login/Password categories but it can affect Logins without saved passwords as well. This is a visual glitch for the banner logic only; the affected items do not show up in the Weak Passwords item list.
0 -
I think I found a bug in the latest Windows Beta:
A document should not have a "weak password" because there is no field for a password :)1Password Version: 7.3.642
Extension Version: Not Provided
OS Version: Win10
Sync Type: Not Provided0 -
Hi @majortom,
I've merged your thread into the previous bug report. Please read my reply above yours.
Thanks for reporting it.
0 -
This should be fixed now in the 1Password 7.3 Beta 6 update.
0