network profile
| bio | website | |
|---|---|---|
| location | ||
| age | 47 | |
| visits | member for | 1 year |
| seen | May 12 '12 at 7:53 | |
| stats | profile views | 0 |
Software designer by passion.
|
May 10 |
comment |
Chinese Remainder Theorem and RSA +1 for the very comprehensive work you've done here |
|
May 10 |
awarded | Scholar |
|
May 10 |
accepted | Encryption with “constant” initialization vector considered harmful |
|
May 9 |
awarded | Supporter |
|
May 9 |
comment |
Encryption with “constant” initialization vector considered harmful Do i get it right: Using AES/CBC/*Padding with an identical, known IV on two short strings of lets say ~10 bytes, where one of them can be very easily deduced/guessed (an item name like "user" in the example above) will reveal the value of item value? |
|
May 9 |
awarded | Student |
|
May 9 |
awarded | Editor |
|
May 9 |
revised |
Encryption with “constant” initialization vector considered harmful added 28 characters in body |
|
May 9 |
comment |
Encryption with “constant” initialization vector considered harmful I meant to improve the question :-) "vault" means simply a password vault or encrypted preference implementation, where "key" and "value" are model properties (->preferences), not encryption related. I changed this in the example. Only "iv" is encryption related. |
|
May 9 |
asked | Encryption with “constant” initialization vector considered harmful |
