Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #6336
| From | Jerry Stuckle <jstucklex@attglobal.net> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: Best practice, (secure), to save session data? |
| Date | 2012-06-15 16:25 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <jrg5np$pas$1@dont-email.me> (permalink) |
| References | (1 earlier) <ud3pa9xp7h.ln2@news.roaima.co.uk> <jrd3jo$4an$1@dont-email.me> <pr5ra9xa49.ln2@news.roaima.co.uk> <jrf4si$9es$1@dont-email.me> <8f0sa9xpqm.ln2@news.roaima.co.uk> |
On 6/15/2012 11:20 AM, Chris Davies wrote: > Jerry Stuckle<jstucklex@attglobal.net> wrote: >> I read it. The thing you miss is the hacker doesn't need to decode the >> encrypted data in the cookie. All he needs to do is send it - just like >> the original client would. > > You're (still?) missing my differentiator between this and a session > cookie. > > >> He won't have the password - but he doesn't need it. > > It wasn't about having a password (implicit with the cookie or otherwise), > it was having access to the data stored directly in the cookie itself. > > Chris It would help if you were to quote the relevant comments. You said: "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." As I stated - this is not correct. No one needs to "brute force the data string" to get logged in - all they have to do is send the cookie. -- ================== 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