Details
-
Bug
-
Resolution: Done
-
Major - P3
-
3.2.9
-
Fully Compatible
-
ALL
-
v3.2
-
-
Platforms 2017-03-27
-
0
Description
DBDirectClient doesn't have a port/session (3.2 versus master), so failures in auth (which try to look up the remote address when forming an error) crash the server or trigger a verify.
Attachments
Issue Links
- related to
-
SERVER-33648 Attempting to perform user- and role-management commands in db.eval() with nolock=false can lead to deadlock
-
- Closed
-
-
SERVER-26257 DBDirectClient should not support auth
-
- Closed
-