Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since you're trying to hide text, which will be visible in the simple dump of the program, you can use some kind of simple encryption to obfuscate your program and hide that text from prying eyes. </p> <h3>Detailed instuctions:</h3> <ol> <li>Visit <a href="http://ROT13.com" rel="nofollow noreferrer">ROT47.com</a> and encode your text online. You can also use <a href="http://www.senses0.org.mv/popzees/rot/rotn.php" rel="nofollow noreferrer">this web site</a> for a more generic ROTn encoding.</li> <li>Replace contents of your string constants with the encoded text.</li> <li>Use the decoder in your code to transform the text back into its original form when you need it. <a href="http://en.wikipedia.org/wiki/ROT13#Implementation" rel="nofollow noreferrer">ROT13 Wikipedia article</a> contains some notes about implementation, and here is <a href="https://stackoverflow.com/questions/3408586/need-a-rot47-javascript-implementation">Javascript implementation of ROTn</a> on StackOverflow. It is trivial to adapt it to whatever language you're using.</li> </ol> <h3>Why use ROT47 which is notoriously weak encryption?</h3> <p>In the end, your code will look something like this:</p> <blockquote> <p>decryptedData = decryptStr(MY_ENCRYPTED_CONSTANT)<br> useDecrypted(decryptedData)</p> </blockquote> <p>No matter how strong your cypher, anybody equipped with a debugger can set a breakpoint on <code>useDecrypted()</code> and recover the plaintext. So, strength of the cypher does not matter. However, using something like Rot47 has two distinct advantages:</p> <ol> <li>You can encode your text online, no need to write a specialized program to encode your text.</li> <li>Decryption is very easy to implement, so you don't waste your time on something that does not add any value to your customers.</li> <li>Anybody reading your code (your coworker or yourself after 5 years) will know immediately this is not a real security, but security by obscurity.</li> <li>Your text will still appear as gibberish to anyone just prying inside your compiled program, so mission accomplished.</li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POHow to hide literals in code
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. UShaimg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to hide literals in code
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI was thinking on text rather than ints. Rot13 seems to me too standard.
      singulars
      1. PO
      1. USMister Smith
    2. COSince you cannot really hide these strings from someone equipped with a debugger, you're hiding them from a casual curious eyes. So, any weak encryption will do there. Don't want a standard Rot13? Add an extra XOR or something...
      singulars
      1. PO
      1. UShaimg
    3. COI think this is the only generic solution. Applying a transformation to text literals, such as RotN or similar. Same with ints.
      singulars
      1. PO
      1. USMister Smith
 

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