[SERVER-14713] mongo shell default ssl behavior Created: 29/Jul/14 Updated: 11/Jul/16 Resolved: 24/Sep/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security, Shell |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.7 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cory Mintz | Assignee: | Amalia Hawkins |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
When using the mongo shell to connect to a mongod/mongos running with ssl, there would be less confusion over the shell's behavior if the user had to explicitly say whether they wanted certificate verification or don't. i.e. you must specific either --sslCAFile or --skipCertificateCheck |
| Comments |
| Comment by Githook User [ 26/Sep/14 ] |
|
Author: {u'username': u'hawka', u'name': u'Amalia Hawkins', u'email': u'amalia.hawkins@10gen.com'}Message: |
| Comment by Githook User [ 26/Sep/14 ] |
|
Author: {u'username': u'hawka', u'name': u'Amalia Hawkins', u'email': u'amalia.hawkins@10gen.com'}Message: |
| Comment by Githook User [ 25/Sep/14 ] |
|
Author: {u'username': u'hawka', u'name': u'Amalia Hawkins', u'email': u'amalia.hawkins@10gen.com'}Message: |
| Comment by Githook User [ 25/Sep/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: Revert " This reverts commit 0c46836a9befaff86825a8238027c8b4223ca14c. |
| Comment by Githook User [ 24/Sep/14 ] |
|
Author: {u'username': u'hawka', u'name': u'Amalia Hawkins', u'email': u'amalia.hawkins@10gen.com'}Message: |
| Comment by Eric Milkie [ 29/Jul/14 ] |
|
In 2.7.4, we added a feature to the server so it will no longer start if it has an expired or invalid certificate: |