*Blink* So much for rhetorical questions. I'm impressed. Now I know who to pester if I ever have questions. :-)
I should clarify: I was numbering the arrows on a diagram, trying to make sense of the process. In this case there were separate arrows and descriptions for requests and responses, so they counts as two hops. By your description that adds up to 16 hops. Again, complicated, but it will probably do the job it was designed for. I just don't look forward to ever implementing it.
Yes, the quickest possible is pre-authenticating with Basic, so you only get one request and one response, 2 hops (and everybody in between knows your password). Everything else just gets more complex from there.
Personally I look forward to the day when someone comes up with a security mechanism that isn't based on the concept of "If you jump through x hoops exactly right, and cross your fingers, then I won't break what you were trying to do." Sadly, I expect this wish is right up there with "Why can' we all just get along?"
Comments 2
Reply
I should clarify:
I was numbering the arrows on a diagram, trying to make sense of the process. In this case there were separate arrows and descriptions for requests and responses, so they counts as two hops. By your description that adds up to 16 hops. Again, complicated, but it will probably do the job it was designed for. I just don't look forward to ever implementing it.
Yes, the quickest possible is pre-authenticating with Basic, so you only get one request and one response, 2 hops (and everybody in between knows your password). Everything else just gets more complex from there.
Personally I look forward to the day when someone comes up with a security mechanism that isn't based on the concept of "If you jump through x hoops exactly right, and cross your fingers, then I won't break what you were trying to do." Sadly, I expect this wish is right up there with "Why can' we all just get along?"
Reply
Leave a comment