[SERVER-39987] Refactor EncryptionKeyManager to make WiredTiger use more generic Created: 06/Mar/19 Updated: 29/Oct/23 Resolved: 21/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jonathan Reams | Assignee: | Jonathan Reams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Security 2019-03-11, Security 2019-03-25 | ||||||||
| Participants: | |||||||||
| Description |
|
Right now we are using the WiredTiger C API directly in the ESE keystore and there are a lot of assumptions about having a fixed schema in the way we use it. Since we are about to have a v0 and v1 schema, we should refactor our WT usage so it's more generic and can easily handle multiple schemas. |
| Comments |
| Comment by Githook User [ 21/Mar/19 ] |
|
Author: {'email': 'jbreams@mongodb.com', 'name': 'Jonathan Reams', 'username': 'jbreams'}Message: |