[SERVER-31407] audit wire version checks to ensure we reject or close connections from clients with binary versions that are too old Created: 05/Oct/17  Updated: 19/Oct/17  Resolved: 19/Oct/17

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

Type: Bug Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding 2017-10-23
Participants:

 Description   

This ticket should update the places where we check a client's wire protocol version to

  • decide what maxWireVersion to send back in the isMaster handshake (to make the client fail to connect if it's too old)
  • decide whether to close client connections from clients that are too old
  • decide whether a shard is too old to add to a cluster

particularly to check "in any state other than fully downgraded to 3.4" rather than just checking "in 3.6."



 Comments   
Comment by Esha Maharishi (Inactive) [ 19/Oct/17 ]

Closing as a duplicate of the work done to produce this document in an in-person meeting: https://docs.google.com/document/d/1j8fSzlSyEd9Rzw-C0d-1uhnyFYXmtj2us5wjeVOXqkA/edit#

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