Re: Re: Re: Re: The sound of one cookie (not) authenticatingby arhuman (Vicar)
|on Apr 03, 2001 at 17:31 UTC||Need Help??|
Instead the issue is that customers can mistakenly give away a link into their session just by giving the current URL to someone else.
Ok I may have missed the question, it thought it was What's the best way to avoid Joe Blow having access to the original shoppers cart?.
I don't understand how computing a hash will prohibit sessions from being transferred with URLs
The hash use is only to one way to secure a parameter (verbatim from my post)
A parameter hashed this way can't be used in another session nor faked.
Is the server or the browser going to compute the hash?
The server, beccause only the server knows the 'private value'...
If the server, then the URL is usable by any browser (which means that it can be given to others along with the hashed session ID)
As the hash value is bound to an id session you just can't use it with another session !
So you can't reuse and old hash value nor even compute it (if you know your id session) to feed it to the server as you don't know the private value...
"Only Bad Coders Badly Code In Perl" (OBC2IP)