Microsoft Windows 中的泄露防护：修订间差异
跳转到导航
跳转到搜索
小
→Windows 8 至 Windows 10 11 月更新
| 第 35 行： | 第 35 行： | ||
Throughout the development timeframes of [[Windows 8]] and [[Windows 10 November Update]], an updated version of the Windows Fingerprinting Service was implemented in a similar fashion to the unique identifier mechanism first included as part of [[Windows XP]], designed in such a way that the fingerprint be present in every leaked Windows build irrespective of the amount of times the build is repacked. | Throughout the development timeframes of [[Windows 8]] and [[Windows 10 November Update]], an updated version of the Windows Fingerprinting Service was implemented in a similar fashion to the unique identifier mechanism first included as part of [[Windows XP]], designed in such a way that the fingerprint be present in every leaked Windows build irrespective of the amount of times the build is repacked. | ||
Early implementations of leak prevention were initially present in the form of a simple wallpaper replacement and a warning in <code>[[winver]]</code> in [[Windows 8 Build 7762.0.fbl_grfx_dev1.100613-1700|build 7762]], and was later iterated upon through the introduction of a fingerprint blob and a dedicated confidentiality warning between [[Windows 8 Build 7785.0.fbl_grfx_dev1.100721-1700|build 7785]] and [[Windows 8 Build 7875.0.fbl_grfx_dev1.101102-1700|build 7875]], which are shown on the [[ | Early implementations of leak prevention were initially present in the form of a simple wallpaper replacement and a warning in <code>[[winver]]</code> in [[Windows 8 Build 7762.0.fbl_grfx_dev1.100613-1700|build 7762]], and was later iterated upon through the introduction of a fingerprint blob and a dedicated confidentiality warning between [[Windows 8 Build 7785.0.fbl_grfx_dev1.100721-1700|build 7785]] and [[Windows 8 Build 7875.0.fbl_grfx_dev1.101102-1700|build 7875]], which are shown on the [[水印|desktop watermark]] and are displayed by the <code>shell32.dll</code> dynamic link library. The fingerprint is directly appended at the end of the <code>BuildLab</code> string (queried from registry key <code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion</code>) in the form of a build hash (officially named the "EULA hash"), computed by splitting the WFS blob into 8 arrays of 16 bytes and XORing each of the 16 bytes together. The EULA hash can then be derived in order to source build leaks to existing Microsoft affiliates; the visibility of the EULA hash and the confidentiality warnings depend on the presence of certain compiler flags. | ||
{{multiple image | {{multiple image | ||