[MONGOCRYPT-102] libmongocrypt: tightly integrate libcrypto components Created: 07/Jun/19  Updated: 04/Sep/19  Resolved: 10/Jun/19

Status: Closed
Project: Libmongocrypt
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Roberto Sanchez Assignee: Roberto Sanchez
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Development of the Java bindings has revealed that a libmongocrypt.so built on Ubuntu will not work on RedHat and that a libmongocrypt.so built on RedHat will not work on Ubuntu. The source of the problem has to do with the differing naming conventions for libssl components (of which libcrypto is a part) between the two distributions. Additionally, the versioning of libssl components on the various supported distributions further complicates the production of a single libmongocrypt.so which works on all supported Linux variants.

This problem will also affect the Python and C# drivers, and possibly others.

To address this problem, it is necessary to vendor the libssl code into the libmongocrypt project. The build should be updated so that specifying an optional build flag results in the libcrypto components that are used by libmongocrypt being built and linked directly into the resulting libmongocrypt.so so that there is no external dependency on libssl or libcrypto.



 Comments   
Comment by Jeffrey Yemin [ 10/Jun/19 ]

That's right.  I'll close as Won't Fix.

Comment by Kevin Albertson [ 10/Jun/19 ]

Since we decided not to vendor parts of OpenSSL, does this ticket no longer apply?

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