You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-26Lines changed: 1 addition & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -162,35 +162,10 @@ public class DatabaseContext : DbContext
162
162
}
163
163
```
164
164
165
-
## Important notes
166
-
167
-
### AES Provider structure
168
-
169
-
The following section describes how encrypted fields using the built-in AES provider encrypts data.
170
-
There is two available modes :
171
-
172
-
* Fixed IV
173
-
* Dynamic IV
174
-
175
-
#### Fixed IV
176
-
177
-
A fixed IV is generated at setup and is used for every encrypted fields on the database.
178
-
This might be a security issue depending on your context.
179
-
180
-
#### Dynamic IV
181
-
182
-
For each encrypted field, the provider generates a new IV with a length of `16 bytes`. These 16 bytes are written at the begining of the `CryptoStream` followed by the actual input to encrypt.
183
-
184
-
Similarly, for reading, the provider reads the first **16 bytes** from the input data converted as a `byte[]` to retrieve the initialization vector and then read the encrypted content.
185
-
186
-
For more information, checkout the [`AesProvider`](https://github.com/Eastrall/EntityFrameworkCore.DataEncryption/blob/master/src/EntityFrameworkCore.DataEncryption/Providers/AesProvider.cs#L58) class.
187
-
188
-
> :warning: When using Dynamic IV, you cannot use the Entity Framework LINQ extensions because the provider will generate a new IV per value, which will create unexpected behaviors.
189
-
190
165
## Thanks
191
166
192
167
I would like to thank all the people that supports and contributes to the project and helped to improve the library. :smile:
0 commit comments