[SERVER-10297] Strengthen checks in okForStorage to eliminate production of objects with invalid field names Created: 23/Jul/13 Updated: 02/Aug/18 Resolved: 25/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Write Ops |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.2 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andrew Morrow (Inactive) | Assignee: | Gregory McKeon (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
The current okForStorage misses some edge cases. For the new update framework, we would like to fix these. Marking QA needed since an adversary trying to produce bad field names would be helpful. |