Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POPHP: mcrypt mangles beginning of string to garbage
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScaf
    1. UScaf
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POPHP: mcrypt mangles beginning of string to garbage
      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. VTAcceptedByOriginator
    1. COThanks, not sharing the IV really was the full problem. But I've got a small bonus question: Why am I able to decode everything after the first ~30 bytes correctly? The key is only 32 byte long since I can't use any longer key (PHP will throw an error); is a part of my message unprotected from decryption? I think I don't need mhash since I only need encryption to protect (critical) temporary data in a database? (deleted after 10 minutes; only read access matters, manipulations without read access don't)
      singulars
      1. PO
      1. USEnergiequant
    2. COThat's because of the way CFB works - the IV is only needed to decrypt the first block. To decrypt the second block, the ciphertext of the first block is what's needed (and you were transmitting that, and all subsequent blocks, fine). This is why an HMAC is a good idea - the attacker can flip *any* bits of your message at will, undetectably - so if he can guess what you were saying (eg, "admin=0"), he can make you say whatever he wants (eg, "admin=1").
      singulars
      1. PO
      1. UScaf
    3. COOkay, so the IV is only important to protect the first block (should be 16 bytes for Rijndael 256?) so one can safely store a hash there by adding the IV as some kind of salt to check for manipulations? But if I don't need that extra protection I would be fine to use an empty IV as well (or no IV at all if that's possible) and would still not sacrifice any security of all blocks except the first one because everything after the first block will always be decryptable with whatever random IV I choose?
      singulars
      1. PO
      1. USEnergiequant
 

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