Jump to content

Recommended Posts

If the session data is saved as an unencrypted cookie then it is very easy to edit. If it's saved as an encrypted cookie or saved in a database then it is much more secure. However, please remember nothing is ever fool proof or completely safe. You have to take security on a per project basis. You need to make cracking your security protocols more effort that the data you hold is worth. For example, no point in using SSL certificates and https if the only thing your holding is food recipes.

Link to comment
https://forums.phpfreaks.com/topic/190551-session-security/#findComment-1005031
Share on other sites

If the session data is saved as an unencrypted cookie...

 

...which it isn't. Only session's ID is stored on client's side. All session data is stored on server. Unless you overwrite default session handlers with something silly that is... ;)

 

 

Link to comment
https://forums.phpfreaks.com/topic/190551-session-security/#findComment-1005035
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.