Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #6329
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: Best practice, (secure), to save session data? |
| Date | 2012-06-14 12:30 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <jrd3jo$4an$1@dont-email.me> (permalink) |
| References | <a3tm2rFqr3U1@mid.individual.net> <ud3pa9xp7h.ln2@news.roaima.co.uk> |
On 6/14/2012 8:52 AM, Chris Davies wrote: > Simon<bad@example.com> wrote: >> the way I see it, if they can get the session cookie then they can >> just as well access the base64_encoded data anyway. > > Almost. > > 1. If you put the data in the session cookie as base64 then it can be > decoded and viewed any time someone likes. No security. > > 2. If you encrypt the data into the cookie using a secret known only to > the website then at least someone has to go to the bother of trying to > brute force the data string, but they have as much time as they like to > do so. Password security. > Incorrect. They don't need to break the string. All they have to do is send the cookie. The server doesn't care which client the cookie came from. > 3. If you put a session key in the cookie with, say, a 4 hour timeout on > the webserver side where the real data is stored, then after the timeout > has expired the session key is useless to anyone trying to obtain your > client's data. Time security. > Yes, but if there's personal data, 4 hours may be too long. > You have to trade off password-based vs time-based security. Generally > #3 is the preferred solution. > > Chris -- ================== Remove the "x" from my email address Jerry Stuckle JDS Computer Training Corp. jstucklex@attglobal.net ==================
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Best practice, (secure), to save session data? Simon <bad@example.com> - 2012-06-14 10:35 +0200
Re: Best practice, (secure), to save session data? Jerry Stuckle <jstucklex@attglobal.net> - 2012-06-14 07:46 -0400
Re: Best practice, (secure), to save session data? Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-14 13:52 +0100
Re: Best practice, (secure), to save session data? Jerry Stuckle <jstucklex@attglobal.net> - 2012-06-14 12:30 -0400
Re: Best practice, (secure), to save session data? Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-15 08:46 +0100
Re: Best practice, (secure), to save session data? Jerry Stuckle <jstucklex@attglobal.net> - 2012-06-15 07:04 -0400
Re: Best practice, (secure), to save session data? Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-15 16:20 +0100
Re: Best practice, (secure), to save session data? Jerry Stuckle <jstucklex@attglobal.net> - 2012-06-15 16:25 -0400
Re: Best practice, (secure), to save session data? Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-18 19:02 +0100
Re: Best practice, (secure), to save session data? Jerry Stuckle <jstucklex@attglobal.net> - 2012-06-18 15:13 -0400
Re: Best practice, (secure), to save session data? Chris Davies <chris-usenet@roaima.co.uk> - 2012-06-18 23:12 +0100
Re: Best practice, (secure), to save session data? Jerry Stuckle <jstucklex@attglobal.net> - 2012-06-18 21:30 -0400
Re: Best practice, (secure), to save session data? Arno Welzel <usenet@arnowelzel.de> - 2012-06-19 08:37 +0200
Re: Best practice, (secure), to save session data? Arno Welzel <usenet@arnowelzel.de> - 2012-06-15 22:44 +0200
csiph-web