Initializing client-side encryption spawns mongocryptd even if crypt_shared is available and loaded

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Unknown
    • 1.23.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      When initializing client-side encryption, if the user has not explicitly disabled the spawning of mongocryptd as part of the CSE options, libmongoc will attempt to spawn mongocryptd. If crypt_shared is loaded, libmongoc does not required mongocryptd to perform query analysis, and should not spawn it.

      How to Reproduce

      If CSE options are set such that mongocryptd would be spawned by libmongoc in the absence of crypt_shared, libmongoc will attempt to spawn mongocryptd regardless of whether crypt_shared is available and loaded.

      Additional Background

      The specification modifications for the addition of the crypt_shared library as part of encryption mandates that mongocryptd must not be spawned if libmongocrypt reports successfully loaded crypt_shared. The guard for this condition is missing from _mongoc_crypt_new.

            Assignee:
            Colby Pike
            Reporter:
            Colby Pike
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: