Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Basically, anyone with access to your program and a debugger <em>can</em> and <em>will</em> find the key in the application if they want to.</p> <p>But, if you just want to make sure the key doesn't show up when running <code>strings</code> on your binary, you could for instance make sure that the key is not within the printable range.</p> <p><strong>Obscuring key with XOR</strong></p> <p>For instance, you could use XOR to split the key into two byte arrays:</p> <pre><code>key = key1 XOR key2 </code></pre> <p>If you create key1 with the same byte-length as <code>key</code> you can use (completely) random byte values and then compute <code>key2</code>:</p> <pre><code>key1[n] = crypto_grade_random_number(0..255) key2[n] = key[n] XOR key1[n] </code></pre> <p>You can do this in your build environment, and then only store <code>key1</code>and <code>key2</code> in your application.</p> <p><strong>Protecting your binary</strong></p> <p>Another approach is to use a tool to protect your binary. For instance, there are several security tools that can make sure your binary is obfuscated and starts a virtual machine that it runs on. This makes it hard(er) to debug, and is also the convential way many commercial grade secure applications (also, alas, malware) is protected.</p> <p>One of the premier tools is <a href="http://www.oreans.com/products.php" rel="noreferrer">Themida</a>, which does an awesome job of protecting your binaries. It is often used by well known programs, such as Spotify, to protect against reverse engineering. It has features to prevent debugging in programs such as OllyDbg and Ida Pro.</p> <p>There is also a larger list, maybe somewhat outdated, of <a href="http://www.google.com/Top/Computers/Security/Products_and_Tools/Software_Protection_and_License_Control/" rel="noreferrer">tools to protect your binary</a>.<br> Some of them are free.</p> <p><strong>Password matching</strong></p> <p>Someone here discussed hashing password+salt. </p> <p>If you need to store the key to match it against some kind of user submitted password, you should use a one-way hashing function, preferrably by combining username, password and a salt. The problem with this, though, is that your application has to know the salt to be able to do the one-way and compare the resulting hashes. So therefore you still need to store the salt somewhere in your application. But, as @Edward points out in the comments below, this will effectively protect against a dictionary attack using, e.g, rainbow tables.</p> <p>Finally, you can use a combination of all the techniques above.</p>
    singulars
    1. This table or related slice is empty.
    1. POtechniques for obscuring sensitive strings in C++
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScsl
    1. UScsl
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POtechniques for obscuring sensitive strings in C++
      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. COIf its a password that the user has to enter, store the hash+salt of the password. See answer below.
      singulars
      1. PO
      1. UShplbsh
    2. CO@hapalibashi: How do you store the salt securely in your application? I don't think the OP needed a one-way password matching system, just a generalized way of storing static keys.
      singulars
      1. PO
      1. UScsl
    3. COI've found when looking at disassembled programs there typically aren't very many XORs, so if you're hoping to use XOR to obscure something, keep in mind they draw attention to themselves.
      singulars
      1. PO
      1. USkb.
 

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