News for hackers. Stuff that matters.

A comment on Interactive example of how Facebook leaked access tokens.

Re:Interactive example of how Facebook leaked access tokens by alangpierce on Wednesday October 17, 2018 @09:08AM (#18238550)
I'm getting errors whenever I visit, but was able to load the "mission" page earlier and see the format (though it also had errors; the center page didn't load at all). Seems like a great idea for explaining these sorts of things!
[ Parent | on HN ]
Re:Interactive example of how Facebook leaked access tokens by ibero on Wednesday October 17, 2018 @09:38AM (#18238786)
The url is incorrect above, it should be https://history.adversary.io/missions/facebook, the above url includes the "/birthday" which causes the 400
[ Parent | on HN ]
Re:Interactive example of how Facebook leaked access tokens by m348e912 on Wednesday October 17, 2018 @10:09AM (#18239151)
The link you posted redirects to https://history.adversary.io/missions/facebook/birthday. It seems to not be working right now.
[ Parent | on HN ]
Re:Interactive example of how Facebook leaked access tokens by cmbuckley on Wednesday October 17, 2018 @10:04AM (#18239090)
It doesn't seem to be caused by that, I've seen the error with and without the /birthday suffix. It looks to be related to missing data from one of the GraphQL responses.
[ Parent | on HN ]
Re:Interactive example of how Facebook leaked access tokens by Glitch-is on Wednesday October 17, 2018 @10:35AM (#18239459)
It should work now
[ Parent | on HN ]