Timeline for Keeping the key and IV safe when AES256 encrypting publicly known data
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:48 | history | edited | CommunityBot |
replaced http://crypto.stackexchange.com/ with https://crypto.stackexchange.com/
|
|
| Mar 9, 2015 at 14:09 | vote | accept | fadedbee | ||
| Mar 9, 2015 at 14:02 | answer | added | Vincent | timeline score: 1 | |
| Mar 9, 2015 at 13:55 | comment | added | Vincent | Nah CBC is probably the best for encrypting files, if you want the difference between mode operations check this and storing the CBC iv is no problem I would recommend you to use a different IV for each file though. | |
| Mar 9, 2015 at 13:31 | comment | added | fadedbee | @VincentAdvocaat CBC, but would/could change to something better | |
| Mar 9, 2015 at 13:13 | comment | added | Vincent | what mode operation are you using? | |
| Mar 9, 2015 at 11:20 | history | edited | fadedbee | CC BY-SA 3.0 |
added 3 characters in body
|
| Mar 9, 2015 at 11:11 | history | edited | fadedbee | CC BY-SA 3.0 |
added 2 characters in body
|
| Mar 9, 2015 at 11:11 | comment | added | fadedbee | @cygnusv Am I correct in thinking that I need to store the (randomly generated) IV with each encrypted file, or there will be no way to decrypt the file? Is if OK for the IV to not be secret? | |
| Mar 9, 2015 at 11:06 | comment | added | cygnusv | Using a different IV for each file is the proper way to do it. | |
| Mar 9, 2015 at 10:58 | history | asked | fadedbee | CC BY-SA 3.0 |