Hi everyone..
I would know what did you think of my method to prevent 'piracy'..
I do like this :
- A Session is made for each user
In the session, put 2 value : a flag userlogged and the userId
- In a cookie, I put the session Id and an unique crypted value.
When user go on private parts of
I would know what did you think of my method to prevent 'piracy'..
I do like this :
- A Session is made for each user
In the session, put 2 value : a flag userlogged and the userId
- In a cookie, I put the session Id and an unique crypted value.
If you're using sessions, there is
I work with double cookie to add a security...
If the user try to change de sessionId, I check with the current sessionId
stored into my own cookie..
But.. It may not to be usefull... :)
The cookie is basically a crypted copy of the session content (with a
different encryption method).
I'm looking
BAROILLER Pierre-Emmanuel wrote:
I work with double cookie to add a security...
This is a common technique and does strengthen security somewhat.
If the user try to change de sessionId, I check with the current sessionId
stored into my own cookie..
But.. It may not to be usefull... :)
The
4 matches
Mail list logo