LastPass Iteration Count - Freely Available?

[rfrazier]

Of course it has.

Thanks but, I'm sorry, that makes no sense. The cache is a temporary data store. It's subject to be overwritten at any time anyway as I understand it. That should have no effect on the permanent settings storage of an extension. I have 8 extensions installed. None of the others is forgetting their settings. Also, LP didn't forget how to log into my account once I give the master password. It remembers the email. It's just forgetting preferences. Unfortunately, some of those preferences are important, like auto logoff. I think it's something that's LP centric. If they depend on a temporary cache for settings storage, that's poor design.

May your bits be stable and your interfaces be fast. Ron

 

[Coffee]

Of course it has. You keep cleaning the cache (another post) and extensions only have the cached data location to save their settings.

This happened to me when I changed my iteration count to 1.1m, then again when I dropped it down to 350k. I suppose changing the iteration count triggers a reset of it's temporary data store.

 

[Coffee]

Correction on my part. The browser extension on my PC in Edge browser was losing its settings from one session to the next. To fix it, I took @CredulousDane's advice and reinstalled the LP extension. That fixed it's problem with losing the settings.

 

[PHolder]

If they depend on a temporary cache for settings storage, that's poor design.

What you consider temporary, the browser considers browser managed. Browsers have MANY ways to store data for sites. There is even a full on database in there ( https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Client-side_web_APIs/Client-side_storage ). The browser manages this data itself, if you interfere, as you have been posting about doing, then you will likely reap what you sow.

Additionally, LastPass having bugs in not news, and no one cares any more.

 

[CredulousDane]

Of course it has. You keep cleaning the cache (another post) and extensions only have the cached data location to save their settings.

I've been cleaning cache (via CCleaner) for a long time every time the browser closes and the resetting of settings was not a problem until a few weeks ago so I wouldn't say the cleaning cache is/was the issue. I started experiencing the issue when I updated my master password. I posted about it over at the LP community and someone else had the same experience. My solution was to re-install the extension.

 

[PHolder]

I've been cleaning cache (via CCleaner)

If you genuinely want your browser to clean up after itself, simply set the settings built into the major ones to have it do so. CCleaner is a placebo--the OS will do a fine job managing things for itself, and if you have something to hide, that you want cleaned up, then you should be using better opsec.

Anyway, rfraiser made posts about extreme cleaning his browser, and it seems very likely he overdid it, and caused whatever problems he had for himself. If that's not the case, then as I said elsewhere, LastPass problems are not news to anyone here and aren't really worthy of further comments, IMHO.

 

[rfrazier]

If that's not the case, then as I said elsewhere, LastPass problems are not news to anyone here and aren't really worthy of further comments, IMHO.

I can't disagree with that statement more. There are currently at least 4 active discussions of LP here on the forum. LP is the biggest, most heavily used, and most trusted password manager. It has many millions of users including myself and a large number of people here on the forum. It has been a key subject in 3 of @Steve 's recent podcasts. If we want to discuss its idiosyncrasies or its fate, then we should be able to do that. This thread, by definition, is about LP. I do not believe I've brought my problems on myself. ANY competent browser extension should be able to survive a cache clearing procedure. Users are often told to clear their cache as a web troubleshooting tactic. In fact, it's one of the first things those users are told to do. Brave specifically has a clear data function in the settings menu, which they obviously anticipate us using. 7 of my 8 extensions are plenty happy and LP is the only one malfunctioning in this way. I believe there's something flaky in the LP extension itself. That's why we're discussing it, to possibly try to figure out how to solve the problem. Also, as discussed in the other thread on cache clearing, I get problems on Amazon by NOT clearing the cache.

May your bits be stable and your interfaces be fast. Ron

 

[PHolder]

There are currently at least 4 active discussions of LP here

They're discussions about how LP screwed up, and how people can recover and leave the,

most trusted password manager

It is anything but. As Steve suggested, people are leaving LP in droves, and going to BitWarden. LP's parent company LogMeIn just released a bunch of additional bad news. Longer term, the company is unlikely to recover, and survive their screwups... certain they have sustained massive reputational damage.

key subject in 3 of @Steve 's recent podcasts

Did you listen to any of them? It was not good news. Steve basically did everything but tell you to move to BitWarden, as he has done.

survive a cache clearing procedure

There is a right way and a wrong way to do that. It seems to me you were seeking measures outside of the browser, which is not the correct way. It would seem pretty simple for you to conduct an experiment. Set your settings to a known state. Then do whatever you did before, and see if the results are a loss of settings. In my books, that would seem to connect cause to effect.

LP is the only one malfunctioning

As I said, people have been having problems with LP for some time now, LP has had some pretty serious issues, and the results are people leaving LP in droves. Rather than suffer Stockholm Syndrome, maybe you too should move away.