Uploaded image for project: 'Libmongocrypt'
  1. Libmongocrypt
  2. MONGOCRYPT-9

libmongocrypt segfaults if no aws provider data is given, but aws data key creation is requested

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      I accidentally was passing the object:

      { aws: { aws: { accessKeyId: '...', secretAccessKey: '...' } }
      

      rather than just:

      { aws: { accessKeyId: '...', secretAccessKey: '...' } }
      

      which results in a segfault:

      [mbroadst@gorgor node-mongodb-crypt (master ✗)]$ MONGODB_CRYPT_DEBUG=1 node ./node_modules/.bin/mocha test/clientEncryption.test.js
       
       
        ClientEncryption
      (node:4653) DeprecationWarning: current URL string parser is deprecated, and will be removed in a future version. To use the new parser, pass option { useNewUrlParser: true } to MongoClient.connect.
          1) should create a data key with the "local" KMS provider
      INFO mongocrypt_setopt_kms_provider_aws (aws_access_key_id="", aws_access_key_id_len=0, aws_secret_access_key="", aws_secret_access_key_len=0)
      INFO mongocrypt_ctx_setopt_masterkey_aws (region="region", region_len=6, cmk="cmk", cmk_len=3)
      [1]    4651 segmentation fault  MONGODB_CRYPT_DEBUG=1 node ./node_modules/.bin/mocha
      

      Attachments

        Activity

          People

            kevin.albertson@mongodb.com Kevin Albertson
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: