[MONGOCRYPT-16] libmongocrypt reverses the order of key_alt_names Created: 06/Aug/19 Updated: 27/Sep/19 Resolved: 27/Sep/19 |
|
| Status: | Closed |
| Project: | Libmongocrypt |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Shane Harvey | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
When I create a data key with key_alt_names=["first", "second"] the data key document that is generated has these keys in the reverse order, i.e. ["second", "first"]. Is this intentional? |
| Comments |
| Comment by Kevin Albertson [ 06/Aug/19 ] |
|
It is not intentional. Switching the order doesn't effect the way we're querying the key vault when fetching keys. But I suppose it could matter if someone were to send queries to the key vault themselves, by trying to match on the entire array. |