Uploaded image for project: 'PHP Driver: Extension'
  1. PHP Driver: Extension
  2. PHPC-1529

Reset libmongocrypt's key vault client after forking

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.10.0-alpha1, 1.10.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      As discussed in this comment from #1075:

      I think we may need to consider how forking might affect FLE. Consider that this has a reference to two clients (its own and the key vault), and internal operations with the key vault client don't use our API that might conditionally call mongoc_client_reset when needed. I'm not sure how often the key vault client is used over the lifetime of the ClientEncryption object (or libmongoc in general), but perhaps we'll need to consider PID checks like we do for cursors and sessions when certain methods are called or this is destroyed.

      There's probably a more general concern about auto encryption if the key vault is used over the lifetime of an application, too.

      kevin.albertson confirmed that the key vault may be utilized for any operation that utilizes auto encryption, so there is definitely a "general concern" independent of ClientEncryption.

            Assignee:
            andreas.braun@mongodb.com Andreas Braun
            Reporter:
            jmikola@mongodb.com Jeremy Mikola
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: