[SERVER-31757] Skip validation for logical times which would not advance the clock Created: 27/Oct/17 Updated: 30/Oct/23 Resolved: 01/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Samantha Ritter (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Platforms 2017-11-13 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
When the server receives a logical time off the wire which is older than its current time, it does not need to advance the clock. As such, the server does not need to validate the time's signature. This will have the fortuitous side effect of preventing unsigned "internal" clusterTimes from being validated, if an instance of the mongo shell acquires one after having authenticated as __system to perform administrative work. If it reauthenticates, and gossips an old time, the void signature will not fail validation unless it is somehow newer than what the server knew. |
| Comments |
| Comment by Githook User [ 01/Nov/17 ] |
|
Author: {'email': 'samantha.ritter@10gen.com', 'name': 'samantharitter', 'username': 'samantharitter'}Message: |