Source code of Windows XP (NT5)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

98 lines
7.0 KiB

  1. ; crypto.txt
  2. ;
  3. ; This data file shows all files that require CSP signing or are involved with
  4. ; the high encryption pack. It is used by the following scripts to drive processing.
  5. ; 1) public\tools\crypto.cmd (TS cert stuffing, CSP-signing, encrypted installers)
  6. ; 2) bldrules\ispu.cmd (encryption pack generation)
  7. ; 3) encryption pack propagation script
  8. ; 4) miscellaneous verification scripts
  9. ;
  10. ; Need Test sign
  11. ; Path rela- Needs Needs on EP Modify on these
  12. ; tive to Encrypted Local- to be to be Add TS Prod releas for platforms
  13. ;File %binaries% Installer izable? MACd? Signd? Cert? Type share? Intl? where 5=yes
  14. ;[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]
  15. ;----------- ---------- ------------ ------- ------ ------ ------ ---- ------ ------ ---------
  16. ; 128-bit binaries
  17. dssenh.dll . instdss5.dll no yes yes no wks no no i386:ia64:amd64
  18. ipsec.sys . instips5.dll no no no no wks no can -
  19. lsasrv.dll . instlsa5.dll yes no no no wks no yes -
  20. ndiswan.sys . instndi5.dll no no no no wks no can -
  21. rsaenh.dll . instrsa5.dll yes yes yes no wks yes no i386:ia64:amd64
  22. ; 40/56-bit binaries
  23. gpkcsp.dll . - no no yes no wks no no i386:ia64:amd64
  24. sccbase.dll . - no no yes no wks no no i386:ia64:amd64
  25. sccsccp.dll . - no no yes no wks no no i386:ia64:amd64
  26. slbcsp.dll . - no no yes no wks no no i386:ia64:amd64
  27. ; additional high encryption pack files
  28. encpack.sed encpack - yes no no no - no yes -
  29. encpack.inf encpack - yes no no no wks no yes -
  30. enceula.txt noexport - yes no no no wks yes yes -
  31. encread.txt noexport - yes no no no wks yes yes -
  32. ; generated high encryption pack self extracting exe
  33. encpack.exe noexport - no no no no wks yes yes -
  34. ; Add TS certificate to Terminal Services Binaries
  35. termdd.sys . - no no no yes srv no can -
  36. tdasync.sys . - no no no yes srv no can -
  37. tdipx.sys . - no no no yes srv no can -
  38. tdnetb.sys . - no no no yes srv no can -
  39. tdpipe.sys . - no no no yes srv no can -
  40. tdspx.sys . - no no no yes srv no can -
  41. tdtcp.sys . - no no no yes srv no can -
  42. tsddd.dll . - no no no yes srv no can -
  43. rdpdd.dll . - no no no yes srv no can -
  44. rdpwd.sys . - no no no yes srv no can -
  45. rdpwsx.dll . - no no no yes srv no can -
  46. ;
  47. ; Column Key
  48. ;
  49. ; [1] Files involved with crypto signing and/or the high encryption pack encpack.exe creation.
  50. ; [2] Path to file after binplacing it, relative to %binaries%.
  51. ; [3] Encrypted installers contain an encrypted version of their associated 128-bit binary as
  52. ; a resource; they ship in all languages of the product, but will only install their
  53. ; 128-bit binary if the trigger file rsaenhs.dll exists on the machine. The trigger
  54. ; file gets installed upon running encpack.exe. There is a one-to-one correspondence
  55. ; between 128-bit files and encrypted installers.
  56. ; [4] Attribute of 128-bit file, not the encrypted installer; version-stamp only ==> no
  57. ; [5] Crypto MACed (an internal cryptographic checksum requred by FIPS). maccsp is run on image.
  58. ; [6] Crypto signed (not to be confused with PRS/catalog signing). Yes implies the following:
  59. ; ==> Cryptographic signature added to the image by one of the following methods:
  60. ; a) test signature via US build process public\tools\crypto.cmd (from enigma server)
  61. ; b) real signature via crypto team for final build (from the bbn box in the vault)
  62. ; ==> This files is either a CSP (cryptographic service provider) or security package
  63. ; ==> International languages need to release these files binary-identical to what US releases
  64. ; Change column [11]'s fields to turn on/off test signing on a per-platform basis. Any
  65. ; file requiring a signature, no matter how it gets signed, needs to have the value 'yes'
  66. ; in this column.
  67. ; [7] Terminal services certificate added to image. Verify with idw\tscrtvfy.exe.
  68. ; [8] Applicable product types.
  69. ; srv ==> bla, sbs, srv, ent, dtc; installed via tsocenc.inf; they're for terminal services
  70. ; wks ==> wks, per, bla, sbs, srv, ent, dtc; installed via encinst.inf
  71. ; - ==> not applicable to any product, perhaps used to generate sfx
  72. ; [9] Files that need to be on the encryption pack release share.
  73. ; yes ==> needed for media or test installs
  74. ; the media creation script is orville\razzle -p setup\bom\encpack.bat
  75. ; no ==> won't hurt to be present, may be useful for testing purposes
  76. ;[10] Derived info from other columns to clarify what's needed for international languages.
  77. ; Don't have scripts use this column; use the other columns directly instead.
  78. ; no <== the file gets crypto signed
  79. ; can <== the file does not get crypto signed or localized so intl langs have no restrictions
  80. ; yes <== the file does not get crypto signed AND the file gets localized or is
  81. ; necessarily rebuilt for intl
  82. ;[11] This column only applies to files that require signing ([6]==yes).
  83. ; Valid values: any combination of the following: { i386,amd64,ia64 }
  84. ; Test sign binaries on the specified platforms via signcsp.exe and enigma. Otherwise,
  85. ; these files need to be checked in already vault-signed with real signatures for RTM.
  86. ; Platforms need to be colon-delimited with no spaces.
  87. ; Note that when checking in vault-signed files, the idea is that nothing modifies them
  88. ; afterward.
  89. ; a) avoid rebasing by adding to public\tools\never.reb
  90. ; b) let the perf team know to avoid re-optimizing
  91. ; c) crypto.cmd already marks the file not-to-be-rebound
  92. ; d) these files should not be localized, independent of test or real signing.