OMG I wish that someone would tell this to Apple. Apple's developer services, such as App Store Connect, actually use session cookies. It's infuriating.
Frequent reauth doesn't make you more secure
11–20 of 539 posts
Re: Frequent reauth doesn't make you more secure
#12Re: Frequent reauth doesn't make you more secure
#13> What are we really checking? That the security policy for the user and the resulting access key hasn't changed their level of access? Identity, while the most common use case, is only half the system when federating logins.
Re: Frequent reauth doesn't make you more secure
#14Re: Frequent reauth doesn't make you more secure
#15The assumption that basically, device = same person (browser session really) over a long period of time is the right one, 99% of the time.
Sometimes it's appropriate to make much more conservative assumptions. People might be in bad family situations (where not everyone with access to a shared device might be entirely trustworthy) or using a shared computer because they access things from a library, etc.
You can't help much (the computer might as well be compromised) but short session timeouts can make sense.
Re: Frequent reauth doesn't make you more secure
#16Re: Frequent reauth doesn't make you more secure
#17Earlier quoted context omitted.
Uh, session cookies being one of the most fundamental pieces of authentication tech, there's nothing wrong with them. This is like saying, "example.com actually uses HTTPS. It's infuriating." Do you mean that you have to reauth across domains? Those still use session cookies. Edit: I'm dating myself here, but as far as I can tell apparently sometime between 2010 and 2011, developers started referring to session cooki…
No, sites use persistent cookies , which remain on your browser after you have closed the tab. Session cookies are wiped out automatically after every session.
Re: Frequent reauth doesn't make you more secure
#18OMG I wish that someone would tell this to Apple. Apple's developer services, such as App Store Connect, actually use session cookies. It's infuriating.
Uh, session cookies being one of the most fundamental pieces of authentication tech, there's nothing wrong with them. This is like saying, "example.com actually uses HTTPS. It's infuriating." Do you mean that you have to reauth across domains? Those still use session cookies. Edit: I'm dating myself here, but as far as I can tell apparently sometime between 2010 and 2011, developers started referring to session cooki…
Most sites do not use session cookies for auth, they use persistent cookies.