Re: [PHP] non transmitted cookie

2003-02-27 Thread Jason Sheets
That is why I suggested passing all that over SSL which would make it very difficult to get the data even if you were able to get the packets. If you are operating with data that you care about you probably need SSL. There is not much point in creating some type of applet combination that your us

Re: [PHP] non transmitted cookie

2003-02-26 Thread Dennis Gearon
Unless of course, you are listening into the network connection :-) Jason Sheets wrote: > > Not that I am aware of, it seems you would be better off using SSL, if > you are concerned about someone hijacking the sessions you could > generate your own session id (I generate random 80 character sess

Re: [PHP] non transmitted cookie

2003-02-26 Thread Jason Sheets
Not that I am aware of, it seems you would be better off using SSL, if you are concerned about someone hijacking the sessions you could generate your own session id (I generate random 80 character session ids instead of 32) and also limit the life of the session, you could write logic to change the

[PHP] non transmitted cookie

2003-02-26 Thread Dennis Gearon
Is there anyway for a page to save information on a user's computer which is accessible via java or javascript, but doesn't get sent with each HTML request the way a cookie is? I had this idea, patterned after kerberos: 1/ A user logs into a site via a secure link. 2/ A hash salt is stored on t