On Fri, 28 Sep 2007 14:38:47 -0400, Gregory S. wrote:
I absolutely don’t mean to spread FUD here, but isn’t that what Rails 2.0
cookie-based sessions do, and isn’t there some way (not obvious to my
sleep-addled brain) to exploit that?
You missed the “stateless” requirement.
No, I saw it - but I also saw the “how can I be sure” requirement, and I
wasn’t sure that cookie-based solutions met both.
From what Jeremy says about using the nonce - and yes, that’s exactly
I was thinking of - it really depends on the application; if a replay
attack could cause something bad to happen, then you simply can’t be
Looking at the OP’s requirements:
- Post Order —> Return Order Details + Payment Method Form
- Post Order + Payment Method —> Return Order Details + Payment Method +
Sender Details Form
- Post Order + Payment Method + Sender Details —> Return Payment Result
a replay at (2) could result in someone sending along a digitally
key that says “Order 1 large-screen TV, my American Express is XXXX” and
getting back a nice “Sure thing, we’ve verified that digital signature,
what address shall we ship to?” dialog.
So it’s something to consider in the design.
Jay L. |
Boston, MA | My character doesn’t like it when they
Faster: jay at jay dot fm | cry or shout or hit.
http://www.jay.fm | - Kristoffer