-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 3.2.4
-
Component/s: Security
-
Fully Compatible
-
ALL
-
Platforms 2017-07-10, Platforms 2017-07-31, Platforms 2017-08-21, Platforms 2017-09-11
mongo --ssl --sslCAFile tests/certificates/ca.pem --host /tmp/mongodb-27017.sock
MongoDB shell version: 3.2.4
connecting to: /tmp/mongodb-27017.sock:27017/test
2016-04-11T13:08:44.614-0700 E NETWORK [thread1] The server certificate does not match the host name /tmp/mongodb-27017.sock
2016-04-11T13:08:44.614-0700 E QUERY [thread1] Error: socket exception [CONNECT_ERROR] for The server certificate does not match the host name /tmp/mongodb-27017.sock :
connect@src/mongo/shell/mongo.js:226:14
mongo --ssl --sslCAFile tests/certificates/ca.pem --host /tmp/mongodb-27017.sock --sslAllowInvalidHostnames MongoDB shell version: 3.2.4 connecting to: /tmp/mongodb-27017.sock:27017/test 2016-04-11T13:12:22.648-0700 W NETWORK [thread1] The server certificate does not match the host name /tmp/mongodb-27017.sock Server has startup warnings:
Since Unix Domain Sockets are a different beast and it doesn't make any sense to do hostname verification.