[SERVER-11824] SSL-enabled shell hangs forever when connecting to 2.4 SSL-disabled mongod Created: 22/Nov/13  Updated: 10/Dec/14  Resolved: 22/Nov/13

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Valeri Karpov Assignee: Andreas Nilsson
Resolution: Won't Fix Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 Description   

If you try to connect to a 2.4.x mongod which doesn't have SSL enabled from a 2.5.x mongo shell with SSL enabled, the mongod logs will show that it accepted a connection, and the mongo shell will hang forever. Ideally, the shell would exit with a helpful error message and the mongod would log that there was an error with the connection.



 Comments   
Comment by Eric Milkie [ 22/Nov/13 ]

Note that the version of the shell doesn't matter here.

Comment by Daniel Pasette (Inactive) [ 22/Nov/13 ]

It is possible to fix this behavior in the 2.4.9 server but it cannot be fixed on the 2.6 client side without using socket timeouts. We will send a 'SSL Hello' message and wait in a recv() call for something to come back. A 2.4 server won't reply anything to an 'SSL Hello' message.

Generated at Thu Feb 08 03:26:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.