Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-11232

specifying pem file option on shell should automatically indicate ssl option

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 2.5.2
    • Component/s: Security
    • Environment:
      Windows 7 Enterprise Build on 2008 R2
      Git hash:
      mongo - 1ea7e56cb2b8653d4b0453f04728033df34be9e1
      enterprise - d919ef07f817832732d2a0a2ec68251bc161193a
    • ALL
      • mongod started with sslOnNormalPorts and PEM file
      • Connect mongo shell with --sslPEMKeyFile

      This gives
      mongo.exe --sslPEMKeyFile c:\Users\qa377\Downloads\pems\client.pem
      MongoDB shell version: 2.5.3-pre-
      connecting to: test
      2013-10-17T04:33:40.649+0000 Socket recv() errno:10054 An existing connection was forcibly closed by the remote host. 127.0.0.1:27017
      2013-10-17T04:33:40.649+0000 SocketException: remote: 127.0.0.1:27017 error: 9001 socket exception [RECV_ERROR] server [127.0.0.1:27017]
      2013-10-17T04:33:40.665+0000 DBClientCursor::init call() failed
      2013-10-17T04:33:40.680+0000 Error: DBClientBase::findN: transport error: 127.0.0.1:27017 ns: admin.$cmd query:

      { whatsmyuri: 1 }

      at src/mongo/shell/mongo.js:146
      exception: connect failed

      This is same error when connecting without SSL option. Specify the PEM file should default specifying --ssl

            Assignee:
            sverch Shaun Verch (Inactive)
            Reporter:
            sridhar Sridhar Nanjundeswaran (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: