Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'm not sure this provides any sort of security. If a man-in-the-middle attacker wants to change the parameters, all he must do is change the query string and recompute the SHA-1 hash and send that request along to the server.</p> <p>For example, the URL sent by the browser might be:</p> <p><a href="http://www.example.com/addUser.html?parameterA=foo&amp;hash=SHA1" rel="noreferrer">http://www.example.com/addUser.html?parameterA=foo&amp;hash=SHA1</a>("parameterA=foo")</p> <p>If an attacker intercepts this, he can edit it in this way:</p> <p><a href="http://www.example.com/adduser.html?parameterA=bar&amp;hash=SHA1" rel="noreferrer">http://www.example.com/adduser.html?parameterA=bar&amp;hash=SHA1</a>("parameterA=bar")</p> <p>Really, this boils down to the fact you can trust the hash only as much as the parameters themselves.</p> <p>One way you could fix this would be if the user has a password that only he and the server knows, then it would be impossible for the attacker to recompute the hash if he changes the parameters. For example:</p> <p><a href="http://www.example.com/addUser.html?parameterA=foo&amp;hash=SHA1" rel="noreferrer">http://www.example.com/addUser.html?parameterA=foo&amp;hash=SHA1</a>("parameterA=foo"+"theuserpassword")</p> <p>But don't put the password as one of the parameters in the URL :)</p> <p>It is important to note that this isn't the state of the art for verifying the integrity of messages passed between two parties. What is used today is a form of the Hash-based Message Authenticion Code (HMAC) algorithm, which is pretty well described in <a href="http://en.wikipedia.org/wiki/HMAC" rel="noreferrer">HMAC</a>, and definitively in <a href="http://tools.ietf.org/html/rfc2104" rel="noreferrer">RFC2104</a> and <a href="http://csrc.nist.gov/publications/fips/fips198-1/FIPS-198-1_final.pdf" rel="noreferrer">FIPS Pub 198-1</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POPrevent query string manipulation by adding a hash?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJeremy Powell
    1. USJeremy Powell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPrevent query string manipulation by adding a hash?
      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. COYou can simply have a Salt for the Hash to prevent manipulation/man-in-the-middle etc.
      singulars
      1. PO
      1. USDead account
    2. COIf you mean salts that are like /etc/passwd salts, then these don't provide any safety against mitm attacks. Salts are in general public knowledge and only serve to make it more difficult to reverse a hash using brute force attacks. The 'salt' (really the key in a keyed hash) must be secret in order to prevent the attacker from being able to change and recompute the digest. This is basically an authentication scheme, which generally requires some sort of shared secret knowledge before hand.
      singulars
      1. PO
      1. USJeremy Powell
    3. COI think as long as the salt is very random and kept secret, this will be an acceptable solution.
      singulars
      1. PO
      1. USsaille
 

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