Changes between Version 2 and Version 3 of Ticket #354
- Timestamp:
- 03/26/2025 03:13:13 PM (16 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #354 – Description
v2 v3 34 34 If this strange garbage was introduced when the segment was retrieved, the memory page into which the retrieval record was read should have contained all zero bits. 35 35 36 But I believe the entire volume backup of the 1-page segment dumped its entire record onto simulated tape. And this entire record was then reloaded. This means the 1-page segment could have had the unexpected garbage in its on-simulated-disk record, but the garbage w hatshielded from view by the more restrictive bit count on the segment.36 But I believe the entire volume backup of the 1-page segment dumped its entire record onto simulated tape. And this entire record was then reloaded. This means the 1-page segment could have had the unexpected garbage in its on-simulated-disk record, but the garbage was shielded from view by the more restrictive bit count on the segment. 37 37 38 38 At some point in its life-cycle on Multics, this 1-page segment gained what appears to be data from some other segment. This would be a significant security violation.
