vlmcsd.ini.5.unix.txt 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390
  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. PublicIPProtectionLevel
  83. Set the level of protection against KMS activations from public
  84. IP addresses.
  85. 0 = No protection (default)
  86. 1 = Listen on private IP addresses only (plus those specified by
  87. one or more Listen statements)
  88. 2 = Disconnect clients with public IP addresses without activat‐
  89. ing
  90. 3 = Combines 1 and 2
  91. For details on public IP protection levels see vlmcsd(8) command
  92. line option -o.
  93. UseNDR64
  94. Can be TRUE or FALSE. Specifies whether you want to use the
  95. NDR64 transfer syntax. See options -n0 and -n1 in vlmcsd(8). The
  96. default is TRUE.
  97. UseBTFN
  98. Can be TRUE or FALSE. Specifies whether you want to use bind
  99. time feature negotiation in RPC. See options -b0 and -b1 in vlm‐
  100. csd(8). The default is TRUE.
  101. RandomizationLevel
  102. The argument must 0, 1 or 2. This specifies the ePID randomiza‐
  103. tion level. See options -r0, -r1 and -r2 in vlmcsd(8). The
  104. default randomization level is 1. A RandomizationLevel of 2 is
  105. not recommended and should be treated as a debugging level.
  106. LCID Use a specific culture id (LCID) even if the ePID is randomized.
  107. The argument must be a number between 1 and 32767. While any
  108. number in that range is valid, you should use an offcial LCID. A
  109. list of assigned LCIDs can be found at http://msdn.micro‐
  110. soft.com/en-us/goglobal/bb964664.aspx. On the command line you
  111. control this setting with option -C.
  112. MaxWorkers
  113. The argument specifies the maximum number of worker processes or
  114. threads that will be used to serve activation requests concur‐
  115. rently. This is the same as specifying -m on the command line.
  116. Minimum is 1. The maximum is platform specific and is at least
  117. 32767 but is likely to be greater on most systems. The default
  118. is no limit.
  119. ConnectionTimeout
  120. Used to control when the vlmcsd disconnects idle TPC connec‐
  121. tions. The default is 30 seconds. This is the same setting as -t
  122. on the command line.
  123. DisconnectClientsImmediately
  124. Set this to TRUE to disconnect a client after it got an activa‐
  125. tion response regardless whether a timeout has occured or not.
  126. The default is FALSE. Setting this to TRUE is non-standard
  127. behavior. Use only if you are experiencing DoS or DDoS attacks.
  128. On the command line you control this behavior with options -d
  129. and -k.
  130. PidFile
  131. Write a pid file. The argument is the full pathname of a pid
  132. file. The pid file contains is single line containing the
  133. process id of the vlmcsd process. It can be used to stop
  134. (SIGTERM) or restart (SIGHUP) vlmcsd. This directive can be
  135. overriden using -p on the command line.
  136. LogFile
  137. Write a log file. The argument is the full pathname of a log
  138. file. On a unixoid OS and with Cygwin you can use the special
  139. filename 'syslog' to log to the syslog facility. This is the
  140. same as specifying -l on the command line.
  141. LogDateAndTime
  142. Can be TRUE or FALSE. The default is TRUE. If set to FALSE, log‐
  143. ging output does not include date and time. This is useful if
  144. you log to stdout(3) which is redirected to another logging
  145. mechanism that already includes date and time in its output, for
  146. instance systemd-journald(8). If you log to syslog(3), LogDate‐
  147. AndTime is ignored and date and time will never be included in
  148. the output sent to syslog(3). Using the command line you control
  149. this setting with options -T0 and -T1.
  150. LogVerbose
  151. Set this to either TRUE or FALSE. The default is FALSE. If set
  152. to TRUE, more details of each activation will be logged. You use
  153. -v and -q in the command line to control this setting. LogVer‐
  154. bose has an effect only if you specify a log file or redirect
  155. logging to stdout(3).
  156. WhitelistingLevel
  157. Can be 0, 1, 2 or 3. The default is 0. Sets the whitelisting
  158. level to determine which products vlmcsd activates or refuses.
  159. 0: activate all products with an unknown, retail or
  160. beta/preview KMS ID.
  161. 1: activate products with a retail or beta/preview KMS ID
  162. but refuse to activate products with an unknown KMS ID.
  163. 2: activate products with an unknown KMS ID but refuse
  164. products with a retail or beta/preview KMS ID.
  165. 3: activate only products with a known volume license RTM
  166. KMS ID and refuse all others.
  167. The SKU ID is not checked. Like a genuine KMS server vlmcsd
  168. activates a product that has a random or unknown SKU ID. If you
  169. select 1 or 3, vlmcsd also checks the Application ID for cor‐
  170. rectness. If Microsoft introduces a new KMS ID for a new prod‐
  171. uct, you cannot activate it if you used 1 or 3 until a new ver‐
  172. sion of vlmcsd is available.
  173. CheckClientTime
  174. Can be TRUE or FALSE. The default is FALSE. If you set this to
  175. TRUE vlmcsd(8) checks if the client time differs no more than
  176. four hours from the system time. This is useful to prevent emu‐
  177. lator detection. A client that tries to detect an emulator could
  178. simply send two subsequent request with two time stamps that
  179. differ more than four hours from each other. If both requests
  180. succeed, the server is an emulator. If you set this to TRUE on a
  181. system with no reliable time source, activations will fail. It
  182. is ok to set the correct system time after you started vlm‐
  183. csd(8).
  184. MaintainClients
  185. Can be TRUE or FALSE (the default). Disables (FALSE) or enables
  186. (TRUE) maintaining a list of client machine IDs (CMIDs). TRUE is
  187. useful to prevent emulator detection. By maintaing a CMID list,
  188. vlmcsd(8) reports current active clients exactly like a genuine
  189. KMS emulator. This includes bug compatibility to the extent that
  190. you can permanently kill a genuine KMS emulator by sending an
  191. "overcharge request" with a required client count of 376 or more
  192. and then request activation for 671 clients. vlmcsd(8) can be
  193. reset from this condition by restarting it. If FALSE is used,
  194. vlmcsd(8) reports current active clients as good as possible. If
  195. no client sends an "overcharge request", it is not possible to
  196. detect vlmcsd(8) as an emulator with MaintainClients = FALSE.
  197. Maintaining clients requires the allocation of a buffer that is
  198. about 50 kB in size. On hardware with few memory resources use
  199. it only if you really need it.
  200. If you start vlmcsd(8) from an internet superserver, this set‐
  201. ting cannot be used. Since vlmcsd(8) exits after each activa‐
  202. tion, it cannot maintain any state in memory.
  203. StartEmpty
  204. This setting is ignored if you do not also specify Maintain‐
  205. Clients = TRUE. If you specify FALSE (the default), vlmcsd(8)
  206. starts up as a fully "charged" KMS server. Clients activate
  207. immediately. StartEmpty = TRUE lets you start up vlmcsd(8) with
  208. an empty CMID list. Activation will start when the required min‐
  209. imum clients (25 for Windows Client OSses, 5 for Windows Server
  210. OSses and Office) have registered with the KMS server. As long
  211. as the minimum client count has not been reached, clients end up
  212. in HRESULT 0xC004F038 "The count reported by your Key Management
  213. Service (KMS) is insufficient. Please contact your system admin‐
  214. istrator". You may use vlmcs(1) or another KMS client emulator
  215. to "charge" vlmcsd(8). Setting this parameter to TRUE does not
  216. improve emulator detection prevention. It's primary purpose is
  217. to help developers of KMS clients to test "charging" a KMS
  218. server.
  219. ActivationInterval
  220. This is the same as specifying -A on the command line. See vlm‐
  221. csd(8) for details. The default is 2 hours. Example: Activation‐
  222. Interval = 1h
  223. RenewalInterval
  224. This is the same as specifying -R on the command line. See vlm‐
  225. csd(8) for details. The default is 7 days. Example: RenewalIn‐
  226. terval = 3d. Please note that the KMS client decides itself when
  227. to renew activation. Even though vlmcsd sends the renewal inter‐
  228. val you specify, it is no more than some kind of recommendation
  229. to the client. Older KMS clients did follow the recommendation
  230. from a KMS server or emulator. Newer clients do not.
  231. User Run vlmcsd as another, preferrably less privileged, user. The
  232. argument can be a user name or a numeric user id. You must have
  233. the required privileges (capabilities on Linux) to change the
  234. security context of a process without providing any credentials
  235. (a password in most cases). On most unixoid OSses 'root' is the
  236. only user who has these privileges in the default configuration.
  237. This setting is not available in the native Windows version of
  238. vlmcsd. See -u in vlmcsd(8). This setting cannot be changed on
  239. the fly by sending SIGHUP to vlmcsd.
  240. Group Run vlmcsd as another, preferrably less privileged, group. The
  241. argument can be a group name or a numeric group id. You must
  242. have the required privileges (capabilities on Linux) to change
  243. the security context of a process without providing any creden‐
  244. tials (a password in most cases). On most unixoid OSses 'root'
  245. is the only user who has these privileges in the default config‐
  246. uration. This setting is not available in the native Windows
  247. version of vlmcsd. See -g in vlmcsd(8). This setting cannot be
  248. changed on the fly by sending SIGHUP to vlmcsd.
  249. Windows
  250. The argument has the form ePID [ / HwId ]. Always use ePID and
  251. HwId for Windows activations. If specified, RandomizationLevel
  252. for Windows activitations will be ignored.
  253. Office2010
  254. The argument has the form ePID [ / HwId ]. Always use ePID and
  255. HwId for Office 2010 activations. If specified, Randomization‐
  256. Level for Office 2010 activitations will be ignored.
  257. Office2013
  258. The argument has the form ePID [ / HwId ]. Always use ePID and
  259. HwId for Office 2013 activations. If specified, Randomization‐
  260. Level for Office 2013 activitations will be ignored.
  261. Office2016
  262. The argument has the form ePID [ / HwId ]. Always use ePID and
  263. HwId for Office 2016 activations. If specified, Randomization‐
  264. Level for Office 2016 activitations will be ignored.
  265. VALID EPIDS
  266. The ePID is currently a comment only. You can specify any string up to
  267. 63 bytes. In Windows 7 Microsoft has blacklisted few ( < 10 ) ePIDs
  268. that were used in KMSv5 versions of the "Ratiborus Virtual Machine".
  269. Microsoft has given up on blacklisting when KMS emulators appeared in
  270. the wild.
  271. Even if you can use "Activated by cool hacker guys" as an ePID, you may
  272. wish to use ePIDs that cannot be detected as non-MS ePIDs. If you don't
  273. know how these "valid" ePIDs look like exactly, do not use GUIDS in
  274. vlmcsd.ini. vlmcsd provides internal mechanisms to generate valid
  275. ePIDs.
  276. If you use non-ASCII characters in your ePID (you shouldn't do anyway),
  277. these must be in UTF-8 format. This is especially important when you
  278. run vlmcsd on Windows or cygwin because UTF-8 is not the default encod‐
  279. ing for most editors.
  280. If you are specifying an optional HWID it follows the same syntax as in
  281. the -H option in vlmcsd(8) ecxept that you must not enclose a HWID in
  282. quotes even if it contains spaces.
  283. FILES
  284. vlmcsd.ini(5)
  285. AUTHOR
  286. vlmcsd(8) was written by crony12, Hotbird64 and vityan666. With contri‐
  287. butions from DougQaid.
  288. CREDITS
  289. Thanks to CODYQX4, deagles, eIcn, mikmik38, nosferati87, qad, Rati‐
  290. borus, ...
  291. SEE ALSO
  292. vlmcsd(8), vlmcsd(7), vlmcs(1), vlmcsdmulti(1)
  293. Hotbird64 October 2016 VLMCSD.INI(5)