[SERVER-14007] move SSL warning message later in startup Created: 20/May/14 Updated: 05/Jul/16 Resolved: 20/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging, Security |
| Affects Version/s: | 2.6.1 |
| Fix Version/s: | 3.3.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Kinh Hoang |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Security 16 (06/24/16) | ||||
| Participants: | |||||
| Comments |
| Comment by Githook User [ 20/Jun/16 ] |
|
Author: {u'username': u'smcnichols', u'name': u'Sally McNichols', u'email': u'sally.mcnichols@mongodb.com'}Message: |
| Comment by Githook User [ 20/Jun/16 ] |
|
Author: {u'name': u'Hai-Kinh Hoang', u'email': u'haikinh.hoang@mongodb.com'}Message: |
| Comment by Eric Milkie [ 21/May/14 ] |
|
You can make this an official Startup Warning that goes into that particular RamLog. These are the warnings that are displayed when you first connect with the shell, for example. |
| Comment by Andreas Nilsson [ 21/May/14 ] |
|
Eric's suggestions should be an easy fix. The command line checking can be done anytime and it is not actionable since its a warning. |
| Comment by Eric Milkie [ 21/May/14 ] |
|
Perhaps for that specific SSL warning, we should be doing the check later in startup, after command line parsing is finished and the logfile has been established. |
| Comment by Eric Milkie [ 21/May/14 ] |
|
Since the log file is configured by parsing the command line, I don't see how to guarantee that messages from command line parsing go into it. |
| Comment by Spencer Brody (Inactive) [ 20/May/14 ] |
|
Assigning to Matt for triage |