The situation that I have seen come up countless times is that I create a login and password for one site, then eventually that company decides to change its names and stuff and now I have that login and password saved for a second site, when the two are actually the same login & pass for the same site, it just happens to exist behind two separate domain names. For example, microsoft with its microsoft, live, hotmail, and outlook domains (many of them existing at a whole range of different tlds too). Not sure which of those are currently being used, but I’ve seen multiples of those active at any one point in time, and they all took the same login credentials.
Unfortunately, Kaspersky flags this as a security risk in that the password is being reused for a different site.
Right now, my “password check” panel has so many of these duplicate accounts on it that it has rendered the panel basically useless. And given that many of these dual (or more!) sites are still active and accessible from both directions, depending on context, I can’t eliminate either of them, so they continue to clog the password check panel.
Solution: Let us specify and/or combine multiple site logins into one entry so that Kaspersky can recognize that these various sites all use the same account info.
Best answer by Flood and Flood's wife
Solution: Let us specify and/or combine multiple site logins into one entry so that Kaspersky can recognize that these various sites all use the same account info.
Hello
Welcome!
We’re so sorry with the long time it’s taken to reply to your topic
- The issues you’ve identified are similar to KPM, needs an option to acknowledge & continue to use a 'low strength' & or 'not unique' pwd, which
@Anton Mefodys , has added to suggestion #3288279.
Please review, if there’s additional requirements, please share them so they can be included?
- Also,
@Ianh16 has raised Multi site/app passwords, may be of interest.
And, another topic that may be of interest:
- KPM (Password Manager) Search function clears itself after editing an entry, extremely annoying raised by
@Leeham ; again updated by@Anton Mefodys → #4687784, a fix is due in the next patch.
Thank you
Flood+