Traffic analysis¶
Traffic analysis. size.
Retired. This is not a bibliographic entry. Our extractor captured an inline prose definition from an article and stored it as a work. The concept is real; this registry record is a parsing defect. This entry is kept so the citations that pointed at it still resolve, and so the correction is visible rather than silent.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Batching and Delayed Release
- The discipline that guards against this is to keep the schedule provably independent of the protected data and to measure residual timing correlation rather than assume it is gone.
This sourceFixed-schedule batching and constant-volume cover (decoy) traffic are its standard countermeasures, because both sever the correlation between an event and its observable emission.
- The discipline that guards against this is to keep the schedule provably independent of the protected data and to measure residual timing correlation rather than assume it is gone.
- Response Padding or Coarsening
- Message length leaking through encryption is a staple of traffic analysis, and length padding is its standard countermeasure.
This sourceMessage length is a classic leak in this class, and padding messages to uniform sizes is the standard countermeasure.
- Message length leaking through encryption is a staple of traffic analysis, and length padding is its standard countermeasure.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:da7ff2f26201 · see in the full table