On 4/18/09 5:43 PM, John Kristian wrote: > Could you describe an attack scenario, please? I don't know what > 'token shooting' means.
Attempts to invoke the callback URL, guessing tokens (either iterating through brute force or some other pruning technique). > And I don't understand the vulnerability to a replay attack. If an attacker can invoke code at will that's in the _middle_ of an authentication process flow, the end results can be deleterious. Sure, "robust code" should defend against all reasonable attacks, but _why_ put extra burden on the OAuth Consumer when simply signing the callback URL eliminates it all? -- Dossy Shiobara | do...@panoptic.com | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
