Thoughts? I built it a couple years ago! :) Works almost exactly as you said, although you quickly run into problems with how much data you can store in javascript before the page blows up. http://www.senditonthenet.com/
The users password acts as a symmetric key. It is never sent to the server, but a hashed copy is sent to the server for authentication, which is then rehashed and stored in the DB. The users private key is AES encrypted…
I have been through this thought process before. The conclusion I came too was that the implementations should be transparent, but that the user information should not. Basically I was not going to put up a list of…
Thoughts? I built it a couple years ago! :) Works almost exactly as you said, although you quickly run into problems with how much data you can store in javascript before the page blows up. http://www.senditonthenet.com/
The users password acts as a symmetric key. It is never sent to the server, but a hashed copy is sent to the server for authentication, which is then rehashed and stored in the DB. The users private key is AES encrypted…
I have been through this thought process before. The conclusion I came too was that the implementations should be transparent, but that the user information should not. Basically I was not going to put up a list of…