this post was submitted on 01 May 2025
316 points (99.4% liked)
Technology
77816 readers
2245 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So if I understand that correctly that cache is never updated again after it is initially created? Wouldn't that lead to a lot of issues when the online account has its password changed in terms of the new password not working too? Something seems to be missing from this article.
That is addressed in the article
Yeah, but "some cases" is extremely vague. If it is indeed cached indefinitely under all circumstances I would expect changed passwords to never work at all.
If it is just "some cases" it could be anything from the system using a stale cache just when it can not reach the online server (reasonable) over caches still being in some kind of TTL period to some sort of bug.
In typical MS fashion this might be very hard to debug with the hundreds of interacting components./s
In all seriousness they reviewed their internal docs not even the code (likely because it's extremely complex) and said fixing this would brake existing functionality. I think "some cases" is doing heavy lifting for "we know many cases, but won't tell the bad guys out there".