[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:
Depends
is depended on by SERVER-40072 Implement v1 keystore for encrypted s... Closed
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: SERVER-39987 Refactor EncryptionKeyManager to make WiredTiger use more generic
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/fc1a45d5bbd71ebf00559d50a86dce2901345970

Generated at Thu Feb 08 04:53:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.