Wikipedia:Reference desk/Archives/Computing/2023 February 12

= February 12 =

No password is good for MS
I want to condemn Microsoft for what it does with my passwords. I established a new password on Jan 26 of this year and tonight it is invalid. That 26 Jan PW was established in response to MS claim that a previous PW was invalid and that PW was set up in November, I guess. I waste hours retrieving my PWs from my database and creating new ones.! Wikipedia passwords last years without change. Microsoft terrorises us deliberately. Why do they do it? AboutFace 22 (talk) 05:03, 12 February 2023 (UTC)
 * It's unclear what password you're referring to but Microsoft account passwords definitely do not normally become invalid after any set date or time. However for good reason, many vendors do check passwords against leaked password databases (often on login) and require such passwords be changed. If your problem is you're using a leaked password, all I can say is you really shouldn't. If you're re-using passwords, this might be a reason why your password is leaked as many sites have suffered breaches and even when properly hashed, the plain text version of weak passwords will be quickly found. Vendors do sometimes also increase password strength requirements and may require a change of old passwords which don't meet these requirements (again normally on login) although AFAIK Microsoft account requirements are still fairly weak (I think 8 characters without symbols required). Finally vendors may sometimes automatically invalidate passwords if they suspect the account has been compromised, generally forbidding this password from being re-used. Unfortunately such systems are imperfect as one would expect and are vulnerable to false positives especially if you proxies or maybe Tor to login a lot. Turning on multi factor authentication may help reduce such detections. Note if you are using this password for access to services or computers provided by work or school, it's possible they have their own password policies in place which may be more stringent than Microsoft's and could include enforced password changes after some period of time. Nil Einne (talk) 09:09, 12 February 2023 (UTC)
 * It has to do with the encryption bypass processing cache. Passwords are normally stored in a dynamic cloud-based relay environment and only accessible to users delegated by a selection algorithm. Microsoft has gotten around this problem by applying an analytic framework to the encryption sequencing process that allows multiplex bidirectional input/output aggregation. Pretty simple stuff.
 * You can override this default setting by reconfiguring your operating system to parse out encryption keys in a nested virtual framework. It’s easy to figure out and it only takes about 5 minutes. It will also bypass a number of default settings that Microsoft uses to limit cloud-relay analytic processing speed. Dinglepincter (talk) 16:51, 18 February 2023 (UTC)
 * @Dinglepincter, it appears that you are the user who previously edited under the User:Serratra account. You were warned that this kind of silly nonsensical edit is not appropriate, and it's even less appropriate now that you are evading the block that was placed on the Serratra account. Please stop doing this. CodeTalker (talk) 00:13, 19 February 2023 (UTC)