pady...@gmail.com
unread,Feb 1, 2008, 2:56:03 PM2/1/08Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Google Web Toolkit
I am answering my own post - but I have an algo which i wanted some
verification from folks to solve the original problem...how to
establish session id during initial login ( or user setup ) in a
secure way without https...
1. Client - Get user/password
2. Client - Do RPC call and send User
3. Server - Get User and return captcha image url and a salt.
Save user/captcha string, salt on server ( in memory
cache )
4. Client - Show captcha to user ( dynamic load to same screen ) and
get the captcha string.
5. Client - Using Block TEA and sha-256 do encrypt( H(salt,
password) , H( U, captcha) )
Send this to server.
6. Server - Use H(U, captcha) as password to decrypt H(salt,
password ). This also serves as verification.
- Send back verification if decrypt succeeds.
- Save user, H(salt, password ) on server permanently.
7. Save H(salt, password) as session id on client and server.
For authentication in future, use "counter + H ( H(salt, password) +
counter )" on client and server to authenticate.
For password change, do the same as above.
Any suggestions ?
Thx
-- pady