Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POPHP: Preventing Session Hijacking with token stored as a cookie?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USoutis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPHP: Preventing Session Hijacking with token stored as a cookie?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODo you think I should do this in combination with a regular session regeneration and a token or drop the other two and just compare IPs? I suppose the current token does cover this though, since it's salted with the IP of the user trying to gain access. That is to say, spoofing the token of a valid user wouldn't do any good unless you share an IP -- right?
      singulars
      1. PO
      1. USGreg
    2. CODefinitely not in combination. Session regeneration doesn't gain you much in terms of security, but feel free to use it for other purposes. As for the token, a hijacker could generate their own if they could work out the salt (which makes it less salt and more a secret key) rather than stealing the target's token. Considering that data from the client isn't trustworthy and that the main point of sessions is the only thing you need to store on the client is a session ID, drop any scheme that stores data on the client. Server side, the IP (and date) isn't secret, so a hash isn't needed.
      singulars
      1. PO
      1. USoutis
    3. COBe wary of CSRF using this technique. This alone doesn't verify the user's intent, only that they are logged in. An attacker could con them into clicking a link that leads to the action of one of your forms, such as creating a new admin user with the attackers credentials. To prevent that, use your technique in the question to create a hash and add that to the action of the form (and to the session), then compare on the opposite end. Only perform the action if the two values match, meaning the user that clicked on to the action was the same as generated the form in the first place.
      singulars
      1. PO
      1. USDampeS8N
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload