[DRIVERS-2598] Release bindings for libmongocrypt 1.7.3 Created: 05/Apr/23  Updated: 05/May/23  Resolved: 05/May/23

Status: Closed
Project: Drivers
Component/s: Client Side Encryption
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Kevin Albertson Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CDRIVER-4605 Release bindings for libmongocrypt 1.7.3 Closed
split to CSHARP-4601 Release bindings for libmongocrypt 1.7.3 Closed
split to CXX-2666 Release bindings for libmongocrypt 1.7.3 Closed
split to GODRIVER-2798 Release bindings for libmongocrypt 1.7.3 Closed
split to MOTOR-1110 Release bindings for libmongocrypt 1.7.3 Closed
split to NODE-5173 Release bindings for libmongocrypt 1.7.3 Closed
split to PHPLIB-1101 Release bindings for libmongocrypt 1.7.3 Closed
split to PYTHON-3654 Release bindings for libmongocrypt 1.7.3 Closed
split to RUBY-3233 Release bindings for libmongocrypt 1.7.3 Closed
split to RUST-1623 Release bindings for libmongocrypt 1.7.3 Closed
split to JAVA-4923 Update mongodb-crypt dependency to 1.7.3 Closed
Related
is related to MONGOCRYPT-563 "Cryptographic Usage Mask" not includ... Closed
Driver Changes: Needed
Downstream Changes Summary:

Drivers that need to release bindings for libmongocrypt may want to release to get the fix for MONGOCRYPT-563. MONGOCRYPT-563 was released in libmongocrypt 1.7.3.

Drivers that do not require a separate bindings release may not need to take action.

Case:
Engineering Lead: Kevin Albertson Kevin Albertson
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4605 Works as Designed
CXX-2666 Works as Designed
CSHARP-4601 Won't Do
GODRIVER-2798 Works as Designed
JAVA-4923 Fixed 4.9.1
NODE-5173 Won't Do
MOTOR-1110 Duplicate
PYTHON-3654 Fixed pymongocrypt-1.5.2
PHPLIB-1101 Won't Do
RUBY-3233 Fixed 2.19.0
RUST-1623 Done

 Description   

Summary

Drivers that need to release bindings for libmongocrypt may want to release to get the fix for MONGOCRYPT-563.

Drivers that do not require a separate bindings release may not need to take action.

Motivation

MONGOCRYPT-563 prevents use of the KMIP KMS provider with Hashicorp Vault 1.12 to 1.13.0. But users impacted by this bug also have the option of upgrading to Hashicorp Vault 1.13.1.
Creation of DRIVERS ticket to inform teams was requested in slack

Who is the affected end user?

Users of In-Use Encryption using Hashicorp Vault as a KMS provider.

How does this affect the end user?

Cannot use KMIP with Hashicorp Vault without upgrading Hashicorp Vault.

How likely is it that this problem or use case will occur?

Definite if using an affected version of Hashicorp Vault.

If the problem does occur, what are the consequences and how severe are they?

Cannot create data keys with Hashicorp Vault.

Is this issue urgent?

Not sure.

Is this ticket required by a downstream team?

Not sure.

Is this ticket only for tests?

No.

Acceptance Criteria

Users of the driver can use the version of libmongocrypt containing the fix for MONGOCRYPT-563.


Generated at Thu Feb 08 08:25:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.