Databases
StackOverflow2013
Postsdbo
POObfuscating GET id variables with encryption, surrogate key, etc
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POObfuscating GET id variables with encryption, surrogate key, etc
    primarykey
    data
    text
    <p>I'm working on a new application, and in order to obscure the perception of its infancy, I'd like to obscure any instances that could reveal this, for example,<br> <code>$postId=000001</code>. Instead we'd get <code>$postId=sH4d6s8d</code>. Something short-ish, but unique.</p> <p>I've read through a few other questions, unfortunately most answers devolve into security concerns. Application security isn't an issue here, I'm just looking for a way to pass an obscure representation of a row id through GET, and have that URL be sharable, meaning multiple user machines can interpret the obfuscation.</p> <p>I skimmed over surrogate keys for MySQL, XOR, but I'm pretty green and my comprehension went mush quickly. What's the appropriate solution here? Any examples? Thanks.</p> <p><strong>Update</strong></p> <p>Decided on a simple XOR + urlencode solution. i.e:</p> <pre><code>$v = urlencode($var ^ $key) $v = (urldecode($v) ^ $key) </code></pre> <p>From testing so far, this seems great for my purposes. However, looks like Firefox auto-decodes <code>urlencode</code> for display, defeating the whole purpose of the idea:</p> <pre><code>$v = r%5CQXr%5CQXr%5CP &lt;a href="whatevs.php?id=$v"&gt;link&lt;/a&gt; // Firefox renders the below anywhere link is visible (besides source) whatevs.php?id=r\QXr\QXr\P </code></pre> <p>This is annoying. While the id is still obscured and the source is sill "traditionally" urlencoded, those characters don't look natural in a url. But the real problem is anyone who copy/pastes the link won't get the correct resource.</p> <p>Is there a easy fix for this?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPHPeer
    1. USPHPeer
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POObfuscating GET id variables with encryption, surrogate key, etc
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POObfuscating GET id variables with encryption, surrogate key, etc
      1. This table or related slice is empty.
      1. VTUndeletion
    3. VO
      singulars
      1. POObfuscating GET id variables with encryption, surrogate key, etc
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhy don't you seed your IDs at a larger number?
      singulars
      1. POObfuscating GET id variables with encryption, surrogate key, etc
      1. USeggyal
    2. COI agree with @eggyal
      singulars
      1. POObfuscating GET id variables with encryption, surrogate key, etc
      1. USMike Mackintosh
    3. COpossible duplicate of [PHP random URL names (short URL)](http://stackoverflow.com/questions/5422065/php-random-url-names-short-url)
      singulars
      1. POObfuscating GET id variables with encryption, surrogate key, etc
      1. USPeeHaa
 

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