vlmcsd.ini.5.dos.txt 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280
  1. VLMCSD.INI(5) KMS Activation Manual VLMCSD.INI(5)
  2. NAME
  3. vlmcsd.ini - vlmcsd KMS emulator configuration file
  4. SYNOPSIS
  5. vlmcsd.ini
  6. DESCRIPTION
  7. vlmcsd.ini (or simply called the "ini file") is a configuration file
  8. for vlmcsd(8). By default vlmcsd does not use a configuration file. It
  9. is completely optional and for advanced users only. You must use the -i
  10. option on the vlmcsd command line to use an ini file. There is no
  11. default name or default location for the ini file.
  12. Everything, that can be configured in the ini file, may also be speci‐
  13. fied on the command line. Any configuration option specified on the
  14. command line takes precedence over the respective configuration line in
  15. the ini file.
  16. Benefits of a configuration file
  17. While you can use the configuration file to simply modify the default
  18. behavior of vlmcsd, it can also be used to change the configuration of
  19. vlmcsd after you sent a HUP signal(7). Whenever you send SIGHUP, the
  20. configuration file will be re-read. Any changes you made to the ini
  21. file will be reflected after vlmcsd received the hangup signal.
  22. Differences between command line and configuration file
  23. If you specify an illegal option or option argument on the command
  24. line, vlmcsd displays help and exits. If you specify an incorrect key‐
  25. word or argument in the ini file, vlmcsd displays a warning with some
  26. information, ignores the respective line and continues. This is inten‐
  27. tional and prevents vlmcsd from aborting after a SIGHUP if the configu‐
  28. ration was modified incorrectly.
  29. SYNTAX
  30. vlmcsd.ini is a UTF-8 encoded text file with each line being in the
  31. format keyword = argument. The keyword is not case-sensitive. The argu‐
  32. ment is treated literally. It is neither required nor allowed to
  33. enclose the argument in any form of quote characters except when quote
  34. characters are part of the argument itself. Whitespace characters are
  35. ignored only
  36. - at the beginning of a line
  37. - between the keyword and '='
  38. - between '=' and the argument
  39. Lines, that start with '#' or ';' are treated as comments. Empty lines
  40. are ignored as well. If a keyword is repeated in another line, vlmcsd
  41. will use the argument of the last occurence of the keyword. An excep‐
  42. tion to this is the Listen keyword which can be specified multiple
  43. times and causes vlmcsd to listen on more than one IP address and/or
  44. port.
  45. Some arguments are binary arguments that need to be either TRUE or
  46. FALSE. You can use "Yes", "On" or "1" as an alias for TRUE and "No",
  47. "Off" or "0" as an alias for FALSE. Binary arguments are case-insensi‐
  48. tive.
  49. KEYWORDS
  50. The following keywords are defined (not all keywords may be available
  51. depending on the operating system and the options used when vlmcsd(8)
  52. was compiled):
  53. Listen This defines on what combinations of IP addresses and ports vlm‐
  54. csd should listen. Listen can be specified more than once. The
  55. argument has the form ipaddress[:port]. If you omit the port,
  56. the default port of 1688 is used. If the ipaddress contains
  57. colons and a port is used, you must enclose the ipaddress in
  58. brackets. The default is to listen to 0.0.0.0:1688 and [::]:1688
  59. which means listen to all IPv4 and all IPv6 addresses. See the
  60. -L option in vlmcsd(8) for more info about the syntax. If you
  61. use -L or -P on the command line, all Listen keywords in the ini
  62. file will be ignored. The Listen keyword cannot be used if vlm‐
  63. csd has been compiled to use Microsoft RPC (Windows and Cygwin
  64. only) or simple sockets.
  65. Examples:
  66. Listen = 192.168.1.123:1688
  67. Listen = 0.0.0.0:1234
  68. Listen = [fe80::1721:12ff:fe81:d36b%eth0]:1688
  69. Port Can only be used if vlmcsd has been compiled to use simple sock‐
  70. ets or on Windows and Cygwin if vlmcsd(8) has been compiled to
  71. use Microsoft RPC. Otherwise you must use Listen instead. Causes
  72. vlmcsd to listen on that port instead of 1688.
  73. FreeBind
  74. Can be TRUE or FALSE. If TRUE, you can use the Listen keyword
  75. with IP addresses that are currently not defined on your system.
  76. vlmcsd(8) will start listening on these IP addresses as soon as
  77. they become available. This keyword is only available under
  78. Linux and FreeBSD because no other OS currently supports that
  79. feature. FreeBSD supports this only for IPv4 and requires the
  80. PRIV_NETINET_BINDANY privilege which is normally assigned to
  81. proccesses of the root user.
  82. UseNDR64
  83. Can be TRUE or FALSE. Specifies whether you want to use the
  84. NDR64 transfer syntax. See options -n0 and -n1 in vlmcsd(8). The
  85. default is TRUE.
  86. UseBTFN
  87. Can be TRUE or FALSE. Specifies whether you want to use bind
  88. time feature negotiation in RPC. See options -b0 and -b1 in vlm‐
  89. csd(8). The default is TRUE.
  90. RandomizationLevel
  91. The argument must 0, 1 or 2. This specifies the ePID randomiza‐
  92. tion level. See options -r0, -r1 and -r2 in vlmcsd(8). The
  93. default randomization level is 1.
  94. LCID Use a specific culture id (LCID) even if the ePID is randomized.
  95. The argument must be a number between 1 and 32767. While any
  96. number in that range is valid, you should use an offcial LCID. A
  97. list of assigned LCIDs can be found at http://msdn.micro‐
  98. soft.com/en-us/goglobal/bb964664.aspx. On the command line you
  99. control this setting with option -C.
  100. MaxWorkers
  101. The argument specifies the maximum number of worker processes or
  102. threads that will be used to serve activation requests concur‐
  103. rently. This is the same as specifying -m on the command line.
  104. Minimum is 1. The maximum is platform specific and is at least
  105. 32767 but is likely to be greater on most systems. The default
  106. is no limit.
  107. ConnectionTimeout
  108. Used to control when the vlmcsd disconnects idle TPC connec‐
  109. tions. The default is 30 seconds. This is the same setting as -t
  110. on the command line.
  111. DisconnectClientsImmediately
  112. Set this to TRUE to disconnect a client after it got an activa‐
  113. tion response regardless whether a timeout has occured or not.
  114. The default is FALSE. Setting this to TRUE is non-standard
  115. behavior. Use only if you are experiencing DoS or DDoS attacks.
  116. On the command line you control this behavior with options -d
  117. and -k.
  118. PidFile
  119. Write a pid file. The argument is the full pathname of a pid
  120. file. The pid file contains is single line containing the
  121. process id of the vlmcsd process. It can be used to stop
  122. (SIGTERM) or restart (SIGHUP) vlmcsd. This directive can be
  123. overriden using -p on the command line.
  124. LogFile
  125. Write a log file. The argument is the full pathname of a log
  126. file. On a unixoid OS and with Cygwin you can use the special
  127. filename 'syslog' to log to the syslog facility. This is the
  128. same as specifying -l on the command line.
  129. LogVerbose
  130. Set this to either TRUE or FALSE. The default is FALSE. If set
  131. to TRUE, more details of each activation will be logged. You use
  132. -v and -q in the command line to control this setting. LogVer‐
  133. bose has an effect only if you specify a log file or redirect
  134. logging to stdout(3).
  135. ActivationInterval
  136. This is the same as specifying -A on the command line. See vlm‐
  137. csd(8) for details. The default is 2 hours. Example: Activation‐
  138. Interval = 1h
  139. RenewalInterval
  140. This is the same as specifying -R on the command line. See vlm‐
  141. csd(8) for details. The default is 7 days. Example: Activation‐
  142. Interval = 3h. Please note that the KMS client decides itself
  143. when to renew activation. Even though vlmcsd sends the renewal
  144. interval you specify, it is no more than some kind of recommen‐
  145. dation to the client. Older KMS clients did follow the recommen‐
  146. dation from a KMS server or emulator. Newer clients do not.
  147. User Run vlmcsd as another, preferrably less privileged, user. The
  148. argument can be a user name or a numeric user id. You must have
  149. the required privileges (capabilities on Linux) to change the
  150. security context of a process without providing any credentials
  151. (a password in most cases). On most unixoid OSses 'root' is the
  152. only user who has these privileges in the default configuration.
  153. This setting is not available in the native Windows version of
  154. vlmcsd. See -u in vlmcsd(8). This setting cannot be changed on
  155. the fly by sending SIGHUP to vlmcsd.
  156. Group Run vlmcsd as another, preferrably less privileged, group. The
  157. argument can be a group name or a numeric group id. You must
  158. have the required privileges (capabilities on Linux) to change
  159. the security context of a process without providing any creden‐
  160. tials (a password in most cases). On most unixoid OSses 'root'
  161. is the only user who has these privileges in the default config‐
  162. uration. This setting is not available in the native Windows
  163. version of vlmcsd. See -g in vlmcsd(8). This setting cannot be
  164. changed on the fly by sending SIGHUP to vlmcsd.
  165. SPECIAL KEYWORDS
  166. Any valid GUID is being treated as a special keyword in the ini file.
  167. It is used to select a specfic ePID and HwId for an application GUID.
  168. The argument has the form ePID [ / HwId ]. KMS currently knows only 3
  169. application GUIDs:
  170. 55c92734-d682-4d71-983e-d6ec3f16059f (Windows)
  171. 59a52881-a989-479d-af46-f275c6370663 (Office 2010)
  172. 0ff1ce15-a989-479d-af46-f275c6370663 (Office 2013)
  173. To use specific ePIDs for Windows, Office 2010 and Office 2013/2016 you
  174. could add the following lines to vlmcsd.ini:
  175. 55c92734-d682-4d71-983e-d6ec3f16059f = 55041-00206-184-207146-03-1062-6002.0000-3322013
  176. 59a52881-a989-479d-af46-f275c6370663 = 55041-00096-216-598637-03-17418-6002.0000-3312013
  177. 0ff1ce15-a989-479d-af46-f275c6370663 = 55041-00206-234-742099-03-9217-6002.0000-2942013
  178. The ePID is currently a comment only. You can specify any string up to
  179. 63 bytes. In Windows 7 Microsoft has blacklisted few ( < 10 ) ePIDs
  180. that were used in KMSv5 versions of the "ratiborus virtual machine".
  181. Microsoft has given up on blacklisting when KMS emulators appeared in
  182. the wild.
  183. Even if you can use "Activated by cool hacker guys" as an ePID, you may
  184. wish to use ePIDs that cannot be detected as non-MS ePIDs. If you don't
  185. know how these "valid" ePIDs look like exactly, do not use GUIDS in
  186. vlmcsd.ini. vlmcsd provides internal mechanisms to generate valid
  187. ePIDs.
  188. If you use non-ASCII characters in your ePID (you shouldn't do anyway),
  189. these must be in UTF-8 format. This is especially important when you
  190. run vlmcsd on Windows or cygwin because UTF-8 is not the default encod‐
  191. ing for most editors.
  192. If you are specifying an optional HWID it follows the same syntax as in
  193. the -H option in vlmcsd(8) ecxept that you must not enclose a HWID in
  194. quotes even if it contains spaces.
  195. FILES
  196. vlmcsd.ini(5)
  197. AUTHOR
  198. vlmcsd(8) was written by crony12, Hotbird64 and vityan666. With contri‐
  199. butions from DougQaid.
  200. CREDITS
  201. Thanks to CODYQX4, deagles, eIcn, mikmik38, nosferati87, qad, Rati‐
  202. borus, ...
  203. SEE ALSO
  204. vlmcsd(8), vlmcsd(7), vlmcs(1), vlmcsdmulti(1)
  205. Hotbird64 June 2016 VLMCSD.INI(5)