If this is a login for a work/school account, it’s because someone in your IT department thinks that applying a short “max session length” policy is “extra secure”.
Basically no different than shitty password rules or some places that make you change your password every 90 days.
If it makes you feel
worsebetter, those security professionals are usually paid more than most ITs, sometimes over $200k a year.Drives my dad insane because his security person at City Hall might be the dumbest human being alive.
Yeah, my boss routinely shares logins for things over slack group channels. 😟
It could also be that is an application requesting access using an embedded browser, which is basically like an incognito/private window.
it’s because someone in your IT department thinks that applying a short “max session length” policy is “extra secure”.
And that person is right, up to a point at least.
If you hijack my session, a short session lifetime explicitly kicks you out at the end of my original seasion, and you have to re-hijack. Assuming you don’t have both factors, it’s an easy way to limit the foothold of an attacker and make them have to try even harder. Cranking it too low will do the opposite, but we have more than a standard work shift for our session length, and it’s more than long enough to not be a massive annoyance.

I could have lived with Windows 7 for a long time before leaving the platform.
Windows 7 wasn’t Microsoft’s choice. It was the last version they produced under the injunction from the late 90s that prevented them from bundling services with Windows. Otherwise Microsoft actually had Microsoft Accounts (then called .Net Passports) ready to go for XP but had to make it optional. They had planned to tie activation to an account back then.
This also represents the last time the US gave a shit about antitrust.
It was so funny, too, because even back then, they had already set an end-of-life date for 2025.


