If You Configure a Program to Run in Windows 2000 Compatibility Mode, Then It Is Also Vulnerable to Windows 2000 Security Issues¶
Chen, R. (2017). If You Configure a Program to Run in Windows 2000 Compatibility Mode, Then It Is Also Vulnerable to Windows 2000 Security Issues.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Reference Implementation Repository
- Its sharpest failure mode is bug-for-bug compatibility — the reference's accidental behaviors quietly become normative, so downstream implementations copy its quirks and the written spec drifts to match the code rather than the other way around.
This sourceDescribes bug-for-bug compatibility in which compatibility mode preserves an older algorithm, including its security weakness, because software relies on that behavior.
- Its sharpest failure mode is bug-for-bug compatibility — the reference's accidental behaviors quietly become normative, so downstream implementations copy its quirks and the written spec drifts to match the code rather than the other way around.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:4f8872d16c7d · see in the full table