Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>as another answer says, an asymmetric solution is difficult and your best, standard solution is to use a symmetric cipher with a short block size. your restriction to ten characters implies 60 bits with base 64, but you could use a custom encoding to get 64 bits (with a block cipher you need to send an exact number of blocks).</p> <p>if you use a 64 bit block size you will have to fix the IV. in other words, if you send the same number twice, it will be encoded the same way both times [not true! - see neat idea in comments below]. but with a 32 bit block cipher you could use a random IV (padding to hide repeated values). it looks like skip32 would be a good choice - see <a href="https://stackoverflow.com/questions/513056/which-good-block-encryption-algorithm-has-the-shortest-output">Which &quot;good&quot; block encryption algorithm has the shortest output?</a></p> <p>another, ad-hoc idea, that i just pulled out my ass, and which may therefore be insecure is to split your message into two: 32bits and the rest. fill the rest with a random value, which you use as a (zero-padded, if necessary) seed to any stream cipher (<a href="http://en.wikipedia.org/wiki/Stream_cipher" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/Stream_cipher</a>) then xor the value you want to encrypt with the first 32 bits of that (so your final message is the 32bits xor result, plus the random seed).</p> <p>finally, i have no idea why everyone is convinced that these messages will/should/must be insecure. the security does not depend on the message size (it is the key size that is important). as far as i know, small blocks are only weak against long messages. here you do not have a long message (there's an important difference between able to guess a single message in 2^32 and knowing <em>all</em> messages after a similar "small" number of guesses).</p>
    singulars
    1. This table or related slice is empty.
    1. POEncrypt an integer as a human-readable string <= ten characters
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USandrew cooke
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEncrypt an integer as a human-readable string <= ten characters
      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. VTUndeletion
    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. VTAcceptedByOriginator
    1. COActually, that link is almost an exact duplicate of this question. Thanks.
      singulars
      1. PO
      1. USDaniel Coffman
    2. COGregS suggested blowfish, which sounds like a reasonable choice for a a 64 bit block cypher. If you fill the 64 bit block with the 32 bit integer and 32 random bits this should be reasonably secure. There are a few weaknesses inherent in this problem, in particular simply guessing the plaintext has a 1/2^32 chance of succeeding, but I have no idea if that is a relevant attack on how the OP is using his integer.
      singulars
      1. PO
      1. USCodesInChaos
    3. COah, of course. yes, that would work.
      singulars
      1. PO
      1. USandrew cooke
 

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