[MONGOCRYPT-171] Add comment explaining NoPadding for AES in Java wrapper crypto callbacks Created: 09/Aug/19 Updated: 28/Oct/23 Resolved: 27/Sep/19 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | Java binding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
It's confused some readers why the crypto callbacks specify NoPadding for AES encryption when padding is required. The reason is because libmongocrypt does the padding before calling the callback. We should add a comment explaining that. |
| Comments |
| Comment by Githook User [ 27/Sep/19 ] |
|
Author: {'name': 'Jeff Yemin', 'username': 'jyemin', 'email': 'jeff.yemin@10gen.com'}Message: Add comment explaining why the Java binding specify NoPadding for AES
|