One reason for concern was that, as described there, LastPass had a history of security breaches, along with continuing use of undisclosed trackers that observed user activity for marketing purposes. The conclusion to the previous post identified reasons for concern with LastPass, even for users who neither had nor feared what I had experienced. While their advice ultimately did work, it did so by dismantling my MFA protection instead of working with it: it was a matter of fitting a square peg into a round hole, with advice that was designed for a problem that I did not have - that was, in some ways, the opposite of my problem.
#Iobit malist remover how to
Moreover, when I did figure out how to get into my email, I saw that what they sent me looked slipshod and off-target, and might thus confuse or be ignored by some users. Instead, they sent me emails that I did not see until nine hours after my inquiry. In my case, when LastPass did respond, they ignored my request for contact by phone, because I could not get into my email account. They took hours to respond coherently they warned users that a response could require as long as three days and I saw complaints from users who were locked out of their accounts for weeks. The primary failing of LastPass in that situation was the poor quality of its tech support. LastPass, a popular password manager (PM), was a key part of the problem described in the previous post. The present post explores in more detail both those problems and the resulting precautions. At the end of that post, I sketched out some precautions that seemed likely to protect against a recurrence of that unpleasant situation. In that situation, my MFA scheme left me unable to log into most of the websites I used most frequently. In a previous post, I described a situation involving two-factor authentication (2FA, which counts as a form of multifactor authentication, or MFA).
0 kommentar(er)
