News for hackers. Stuff that matters.
Re:An Update on the Security Issue by mehrdadn on Friday October 12, 2018 @02:09PM (#18203396)
Technical question: Does anyone know if there are any common legitimate reasons to allow an authentication system to automatically generate access tokens for a client in response to something other than an actual user login?

The thought of it sounds horrifying to me so I'm wondering if I'm missing something and how/why they might have approved such a design.

Re:An Update on the Security Issue by personamb on Friday October 12, 2018 @02:32PM (#18203603)
Not common at all.

I was an eng at FB when the "View as" feature was being built. I wasn't involved in the project at all, and my memory is hazy (this was probably 7 years ago by now), but I remember people being like "wow this is crazy and probably a bad idea".

I don't actually know if View As generating access tokens was how it worked originally, or if that was a later refactor. Just, in general, spoofing privacy / access control is really scary, no matter how you do it.

However, at the time, Facebook was getting a lot of shit (rightfully) for not helping users understand the privacy model, and the View As feature was actually incredibly useful for helping users understand what was public. So my guess (pure speculation) is that yes, people acknowledged it was scary, but decided the value was worth the cost.

Re:An Update on the Security Issue by techntoke on Friday October 12, 2018 @02:10PM (#18203409)
When you want to gather people's personal and private information and pretend it was a breach.
Re:An Update on the Security Issue by jazzyjackson on Friday October 12, 2018 @02:26PM (#18203565)
Conspiratorial but I like it.