[CXX-2559] Upgrade libmongocrypt dependency to 1.5.2 Created: 29/Jul/22 Updated: 27/Oct/23 Resolved: 31/Jul/22 |
|
| Status: | Closed |
| Project: | C++ Driver |
| Component/s: | Client Side Encryption |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Blocker - P1 |
| Reporter: | PM Bot | Assignee: | Unassigned |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Upstream Changes Summary: | DRIVERS-2403: If possible, pull the affected bindings releases (using libmongocrypt 1.5.0 or 1.5.1) from package managers concurrently with releasing the new package. Use the following blurb for release notes: """ The following conditions will trigger this bug: A GCP-backed or Azure-backed data encryption key being rewrapped requires fetching an access token for decryption of the data encryption key. The result of this bug is that the key material for all data encryption keys being rewrapped is replaced by new randomly generated material, destroying the original key material. To mitigate potential data corruption, upgrade to this version or higher before using RewrapManyDataKey to rotate Azure-backed or GCP-backed data encryption keys. A backup of the key vault collection should always be taken before key rotation. Upgrading to 1.5.2 will result in test failures in some CSFLE unified specification tests with an error like "The parameter is incorrect. HTTP status=400". See |
||||
| Description |
|
This ticket was split from DRIVERS-2403, please see that ticket for a detailed description. |