[SERVER-50333] mongo shell ignores TestData.encryptionCipherMode specified in test suites Created: 17/Aug/20 Updated: 29/Oct/23 Resolved: 22/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Igor Solodovnikov | Assignee: | Adam Cooper (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | Start resmoke with one of the GCM test suites and check what parameters are passed to mongod instances. |
| Sprint: | Security 2020-10-05, Security 2020-10-19, Security 2020-11-02 |
| Participants: |
| Description |
|
There are several test suites for testing encrypted storage with GCM cipher mode:
Those suites assign 'AES256-GCM' value to the TestData.encryptionCipherMode , but the mongo shell ignores it and starts mongod without --encryptionCipherMode parameter. Thus mongod uses default CBC cipher so it wouldn't be testing GCM at all. |
| Comments |
| Comment by Githook User [ 21/Oct/20 ] |
|
Author: {'name': 'Adam Cooper', 'email': 'adam.cooper@mongodb.com', 'username': 'super-cooper'}Message: |
| Comment by Eric Sedor [ 19/Aug/20 ] |
|
Thanks igorsol, I'm passing this on to an appropriate team to take a look. |