Databases
StackOverflow2013
Postsdbo
POSymmetric Encryption (AES): Is saving the IV and Salt alongside the encrypted data safe and proper?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSymmetric Encryption (AES): Is saving the IV and Salt alongside the encrypted data safe and proper?
    primarykey
    data
    text
    <p>I am trying to make sense of how to handle and manage an initilization vector and salt (when applicable) when encrypting and decrypting data using a symmetric encryption algorithm, in this case AES.</p> <p>I have deduced from different SO threads and various other websites that neither the IV or salt need to be secret, only unique in order to defend against cryptanalytic attacks such as a brute-force attack. With this in mind I figured that it would be viable to store my pseudo random IV with the encrypted data. I am asking if the method I am using is proper and furthermore, should I be treating my currently hard coded salt in the same manner? That being writing it to the memory stream along side the IV</p> <p>My code: </p> <pre><code>private const ushort ITERATIONS = 300; private static readonly byte[] SALT = new byte[] { 0x26, 0xdc, 0xff, 0x00, 0xad, 0xed, 0x7a, 0xee, 0xc5, 0xfe, 0x07, 0xaf, 0x4d, 0x08, 0x22, 0x3c }; private static byte[] CreateKey(string password, int keySize) { DeriveBytes derivedKey = new Rfc2898DeriveBytes(password, SALT, ITERATIONS); return derivedKey.GetBytes(keySize &gt;&gt; 3); } public static byte[] Encrypt(byte[] data, string password) { byte[] encryptedData = null; using (AesCryptoServiceProvider provider = new AesCryptoServiceProvider()) { provider.GenerateIV(); provider.Key = CreateKey(password, provider.KeySize); provider.Mode = CipherMode.CBC; provider.Padding = PaddingMode.PKCS7; using (MemoryStream memStream = new MemoryStream(data.Length)) { memStream.Write(provider.IV, 0, 16); using (ICryptoTransform encryptor = provider.CreateEncryptor(provider.Key, provider.IV)) { using (CryptoStream cryptoStream = new CryptoStream(memStream, encryptor, CryptoStreamMode.Write)) { cryptoStream.Write(data, 0, data.Length); cryptoStream.FlushFinalBlock(); } } encryptedData = memStream.ToArray(); } } return encryptedData; } public static byte[] Decrypt(byte[] data, string password) { byte[] decryptedData = new byte[data.Length]; using (AesCryptoServiceProvider provider = new AesCryptoServiceProvider()) { provider.Key = CreateKey(password, provider.KeySize); provider.Mode = CipherMode.CBC; provider.Padding = PaddingMode.PKCS7; using (MemoryStream memStream = new MemoryStream(data)) { byte[] iv = new byte[16]; memStream.Read(iv, 0, 16); using (ICryptoTransform decryptor = provider.CreateDecryptor(provider.Key, iv)) { using (CryptoStream cryptoStream = new CryptoStream(memStream, decryptor, CryptoStreamMode.Read)) { cryptoStream.Read(decryptedData, 0, decryptedData.Length); } } } } return decryptedData; } </code></pre> <p>I am also open to any other information about symmetric encryption with regards to proper practice. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCodesInChaos
    1. USCaster Troy
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSymmetric Encryption (AES): Is saving the IV and Salt alongside the encrypted data safe and proper?
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POSymmetric Encryption (AES): Is saving the IV and Salt alongside the encrypted data safe and proper?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSymmetric Encryption (AES): Is saving the IV and Salt alongside the encrypted data safe and proper?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you are not storing them with your encrypted data, you need to store them somewhere - so YMMV.
      singulars
      1. POSymmetric Encryption (AES): Is saving the IV and Salt alongside the encrypted data safe and proper?
      1. USlarsw
    2. COIn CBC mode, each encrypted block acts as the IV of the next block, so IV being a public value cannot be security relevant - otherwise CBC mode of operation wouldn't be secure. :)
      singulars
      1. POSymmetric Encryption (AES): Is saving the IV and Salt alongside the encrypted data safe and proper?
      1. USvhallac
    3. CO@vhallac well, more the V (vector) as the IV (initialization vector) is can obviously only be the first one.
      singulars
      1. POSymmetric Encryption (AES): Is saving the IV and Salt alongside the encrypted data safe and proper?
      1. USMaarten Bodewes
 

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