Re: Chicken and egg issue with Cookie based login?
From: Julio (julio_at_lalaland.com)
Date: 04/06/05
- Next message: keme: "Re: Almost no user really needs a firewall (was: [OT] Updates of Firefox and Mozilla)"
- Previous message: IPGrunt: "Re: XP shows only 8 characters of (WEP) Network key."
- In reply to: Barry Margolin: "Re: Chicken and egg issue with Cookie based login?"
- Next in thread: Barry Margolin: "Re: Chicken and egg issue with Cookie based login?"
- Reply: Barry Margolin: "Re: Chicken and egg issue with Cookie based login?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 6 Apr 2005 13:59:25 -0400
"Barry Margolin" <barmar@alum.mit.edu> wrote in message
news:barmar-47DA57.08524906042005@comcast.dca.giganews.com...
> In article <deN4e.29753$f%4.23725@bignews1.bellsouth.net>,
> "Julio" <julio@lalaland.com> wrote:
>
> > MAC = MD5("secret key " +
> > MD5("session ID" + "issue date" +
> > "expiration time" + "IP address" +
> > "secret key")
> > )
> >
>
> Cookies are created by the server, not by the client.
Barry,
Thanks for your input.
Of course, a client can create a cookie as well.
> The server generates the hashed cookie and sends it to
> the client.
So in reference to the W3C document, this MAC is created by the server? Not
the client? Then what is the point? In lieu of SSL, how is the user's
credentials obtained by the client, hashed and sent to the server? Via a
COOKIE!
I've seen references to methods where there might be a combination, a
server created QUID cookie just to initialize it. The client uses this with
a new client created hashed cookie to pass the credentials to the server.
Or are you suggesting the above is AFTER the user has been authorized, this
this MAC is a hashed cookie for the authorized session?
> What if you want to allow the same user to login concurrently from
> different clients (e.g. a husband and wife both checking their bank
> account balances)?
This is already handled. Multiple Logins with the same user credential from
different machines is already managed with administrator IP control
preferences. This is aleady designd for BASIC/DIGEST.
Just trying to incorporate a cookie-based login method now. I've looking at
how to pass user credentials to a server as safe as possible using
non-browser popup dialog box BASIC/DIGEST methods
> > Is the "Secret Key" the user's password and the Session ID the user's
name?
>
> The secret key should be a random value generated at login time; if it
> were the user's password, it wouldn't be known only to the server, it
> would also be known by the client.
So the MAC equation as outlined by the W3C is an authorization MAC for a
already logged in session?
That's ok, but that isn't helping. Need to login first. :-)
Unless I read it wrong, sounds to me, the initial passing of user
credentials is less important as maintaining a secured authorized session
key. Is this because it is a one packet transaction client/server exchange
with a minimum window of hacker hijacking?
That doesn't sound right.
Thanks
- Next message: keme: "Re: Almost no user really needs a firewall (was: [OT] Updates of Firefox and Mozilla)"
- Previous message: IPGrunt: "Re: XP shows only 8 characters of (WEP) Network key."
- In reply to: Barry Margolin: "Re: Chicken and egg issue with Cookie based login?"
- Next in thread: Barry Margolin: "Re: Chicken and egg issue with Cookie based login?"
- Reply: Barry Margolin: "Re: Chicken and egg issue with Cookie based login?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|