vlmcsd.ini.5.unix.txt 24 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498
  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. VPN Has to be in the form vpn-adapter-name[=ipv4-address][/cidr-
  94. mask][:dhcp-lease-duration].
  95. Enables a compatible VPN adapter to create additional local IPv4
  96. addresses (like 127.0.0.1) that appear as remote IPv4 addresses
  97. to the system. This allows product activation using a local
  98. instance of vlmcsd. This feature is only available in Windows
  99. and Cygwin builds of vlmcsd since it is not of any use on other
  100. operating systems. Compatible VPN adapters are Tap-windows ver-
  101. sion 8.2 or higher (from OpenVPN) and the TeamViewer VPN
  102. adapter. There is a special vpn-adapter-name. A single period
  103. (.) instructs vlmcsd to use the first available compatible VPN
  104. adapter. The vpn-adapter-name is not case-sensitive. If the vpn-
  105. adapter-name contains spaces (e.g. Ethernet 3), do not enclose
  106. it in quotes.
  107. The default ipv4-address is 10.10.10.9 and the default cidr-mask
  108. is 30. If you are using the default values, your VPN adapter
  109. uses an IPv4 address of 10.10.10.9 and you can set your activa-
  110. tion client to use the easy to remember address 10.10.10.10
  111. (e.g. slmgr /skms 10.10.10.10 or cscript ospp.vbs
  112. /sethst:10.10.10.10).
  113. The dhcp-lease-duration is a number optionally followed by s, m,
  114. h, d or w to indicate seconds, minutes, hours, days or weeks.
  115. The default dhcp-lease-duration is 1d (one day). It is normally
  116. not required to change this value.
  117. It is advised not to manually configure your OpenVPN TAP or
  118. TeamViewer VPN adapter in "Network Connections". If you set the
  119. IPv4 configuration manually anyway, the IPv4 address and the
  120. subnet mask must match the VPN= directive. It is safe leave the
  121. IPv4 configuration to automatic (DHCP). vlmcsd will wait up to
  122. four seconds for the DHCP configuration to complete before bind-
  123. ing to and listenin on any interfaces.
  124. You should be aware that only one program can use a VPN adapter
  125. at a time. If you use the TeamViewer VPN adapter for example,
  126. you will not be able to use the VPN feature of TeamViewer as
  127. long as vlmcsd is running. The same applies to OpenVPN TAP
  128. adapters that are in use by other programs (for example OpenVPN,
  129. QEMU, Ratiborus VM, aiccu, etc.). The best way to avoid con-
  130. flicts is to install Tap-Windows from OpenVPN, cd to C:\Program
  131. Files\TAP-Windows\bin and run addtap.bat to install an addi-
  132. tional TAP adapter. Go to "Network Connections" and rename the
  133. new adapter to "vlmcsd" and specify VPN=vlmcsd to use it.
  134. ExitLevel
  135. Can be either 0 (the default) or 1. Controls under what circum-
  136. stances vlmcsd will exit. Using the default of 0 vlmcsd stays
  137. active as long as it can perform some useful operations. If vlm-
  138. csd is run by any form of a watchdog, e.g. NT service manager
  139. (Windows), systemd (Linux) or launchd (Mac OS / iOS), it may be
  140. desirable to end vlmcsd and let the watchdog restart it. This is
  141. especially true if some pre-requisites are not yet met but will
  142. be some time later, e.g. network is not yet fully setup.
  143. By using ExitLevel = 0 vlmcsd will
  144. exit if none of the listening sockets specified with -L can
  145. be used. It continues if at least one socket can be setup
  146. for listening.
  147. exit any TAP mirror thread (Windows version only) if there
  148. is an error condition while reading or writing from or to
  149. the VPN adapter but continue to work without utilizing a
  150. VPN adapter.
  151. By using ExitLevel = 1 vlmcsd will
  152. exit if not all listening sockets specified with -L can be
  153. used.
  154. exit completely if there is a problem with a VPN adapter it
  155. is using. This may happen for instance if the VPN adapter
  156. has been disabled using "Control Panel - Network - Adapter
  157. Settings" while vlmcsd is using it.
  158. Please note that ExitLevel = 1 is kind of a workaround option.
  159. While it may help under some circumstances, it is better to
  160. solve the problem at its origin, e.g. properly implementing
  161. dependencies in your startup script to ensure all network inter-
  162. faces and the VPN adapter you will use are completely setup
  163. before you start vlmcsd.
  164. UseNDR64
  165. Can be TRUE or FALSE. Specifies whether you want to use the
  166. NDR64 transfer syntax. See options -n0 and -n1 in vlmcsd(8). The
  167. default is TRUE.
  168. UseBTFN
  169. Can be TRUE or FALSE. Specifies whether you want to use bind
  170. time feature negotiation in RPC. See options -b0 and -b1 in vlm-
  171. csd(8). The default is TRUE.
  172. RandomizationLevel
  173. The argument must 0, 1 or 2. This specifies the ePID randomiza-
  174. tion level. See options -r0, -r1 and -r2 in vlmcsd(8). The
  175. default randomization level is 1. A RandomizationLevel of 2 is
  176. not recommended and should be treated as a debugging level.
  177. LCID Use a specific culture id (LCID) even if the ePID is randomized.
  178. The argument must be a number between 1 and 32767. While any
  179. number in that range is valid, you should use an offcial LCID. A
  180. list of assigned LCIDs can be found at http://msdn.micro-
  181. soft.com/en-us/goglobal/bb964664.aspx. On the command line you
  182. control this setting with option -C.
  183. MaxWorkers
  184. The argument specifies the maximum number of worker processes or
  185. threads that will be used to serve activation requests concur-
  186. rently. This is the same as specifying -m on the command line.
  187. Minimum is 1. The maximum is platform specific and is at least
  188. 32767 but is likely to be greater on most systems. The default
  189. is no limit.
  190. ConnectionTimeout
  191. Used to control when the vlmcsd disconnects idle TPC connec-
  192. tions. The default is 30 seconds. This is the same setting as -t
  193. on the command line.
  194. DisconnectClientsImmediately
  195. Set this to TRUE to disconnect a client after it got an activa-
  196. tion response regardless whether a timeout has occured or not.
  197. The default is FALSE. Setting this to TRUE is non-standard
  198. behavior. Use only if you are experiencing DoS or DDoS attacks.
  199. On the command line you control this behavior with options -d
  200. and -k.
  201. PidFile
  202. Write a pid file. The argument is the full pathname of a pid
  203. file. The pid file contains is single line containing the
  204. process id of the vlmcsd process. It can be used to stop
  205. (SIGTERM) or restart (SIGHUP) vlmcsd. This directive can be
  206. overriden using -p on the command line.
  207. LogFile
  208. Write a log file. The argument is the full pathname of a log
  209. file. On a unixoid OS and with Cygwin you can use the special
  210. filename 'syslog' to log to the syslog facility. This is the
  211. same as specifying -l on the command line.
  212. KmsData
  213. Use a KMS data file. The argument is the full pathname of a KMS
  214. data file. By default vlmcsd only contains the minimum product
  215. data that is required to perform all operations correctly. You
  216. may use a more complete KMS data file that contains all detailed
  217. product names. This is especially useful if you are logging KMS
  218. requests. If you don't log, there is no need to load an external
  219. KMS data file.
  220. You may use KmsData = - to prevent the default KMS data file to
  221. be loaded.
  222. LogDateAndTime
  223. Can be TRUE or FALSE. The default is TRUE. If set to FALSE, log-
  224. ging output does not include date and time. This is useful if
  225. you log to stdout(3) which is redirected to another logging
  226. mechanism that already includes date and time in its output, for
  227. instance systemd-journald(8). If you log to syslog(3), LogDate-
  228. AndTime is ignored and date and time will never be included in
  229. the output sent to syslog(3). Using the command line you control
  230. this setting with options -T0 and -T1.
  231. LogVerbose
  232. Set this to either TRUE or FALSE. The default is FALSE. If set
  233. to TRUE, more details of each activation will be logged. You use
  234. -v and -q in the command line to control this setting. LogVer-
  235. bose has an effect only if you specify a log file or redirect
  236. logging to stdout(3).
  237. WhitelistingLevel
  238. Can be 0, 1, 2 or 3. The default is 0. Sets the whitelisting
  239. level to determine which products vlmcsd activates or refuses.
  240. 0: activate all products with an unknown, retail or
  241. beta/preview KMS ID.
  242. 1: activate products with a retail or beta/preview KMS ID
  243. but refuse to activate products with an unknown KMS ID.
  244. 2: activate products with an unknown KMS ID but refuse
  245. products with a retail or beta/preview KMS ID.
  246. 3: activate only products with a known volume license RTM
  247. KMS ID and refuse all others.
  248. The SKU ID is not checked. Like a genuine KMS server vlmcsd
  249. activates a product that has a random or unknown SKU ID. If you
  250. select 1 or 3, vlmcsd also checks the Application ID for cor-
  251. rectness. If Microsoft introduces a new KMS ID for a new prod-
  252. uct, you cannot activate it if you used 1 or 3 until a new ver-
  253. sion of vlmcsd is available.
  254. CheckClientTime
  255. Can be TRUE or FALSE. The default is FALSE. If you set this to
  256. TRUE vlmcsd(8) checks if the client time differs no more than
  257. four hours from the system time. This is useful to prevent emu-
  258. lator detection. A client that tries to detect an emulator could
  259. simply send two subsequent request with two time stamps that
  260. differ more than four hours from each other. If both requests
  261. succeed, the server is an emulator. If you set this to TRUE on a
  262. system with no reliable time source, activations will fail. It
  263. is ok to set the correct system time after you started vlm-
  264. csd(8).
  265. MaintainClients
  266. Can be TRUE or FALSE (the default). Disables (FALSE) or enables
  267. (TRUE) maintaining a list of client machine IDs (CMIDs). TRUE is
  268. useful to prevent emulator detection. By maintaing a CMID list,
  269. vlmcsd(8) reports current active clients exactly like a genuine
  270. KMS emulator. This includes bug compatibility to the extent that
  271. you can permanently kill a genuine KMS emulator by sending an
  272. "overcharge request" with a required client count of 376 or more
  273. and then request activation for 671 clients. vlmcsd(8) can be
  274. reset from this condition by restarting it. If FALSE is used,
  275. vlmcsd(8) reports current active clients as good as possible. If
  276. no client sends an "overcharge request", it is not possible to
  277. detect vlmcsd(8) as an emulator with MaintainClients = FALSE.
  278. Maintaining clients requires the allocation of a buffer that is
  279. about 50 kB in size. On hardware with few memory resources use
  280. it only if you really need it.
  281. If you start vlmcsd(8) from an internet superserver, this set-
  282. ting cannot be used. Since vlmcsd(8) exits after each activa-
  283. tion, it cannot maintain any state in memory.
  284. StartEmpty
  285. This setting is ignored if you do not also specify Maintain-
  286. Clients = TRUE. If you specify FALSE (the default), vlmcsd(8)
  287. starts up as a fully "charged" KMS server. Clients activate
  288. immediately. StartEmpty = TRUE lets you start up vlmcsd(8) with
  289. an empty CMID list. Activation will start when the required min-
  290. imum clients (25 for Windows Client OSses, 5 for Windows Server
  291. OSses and Office) have registered with the KMS server. As long
  292. as the minimum client count has not been reached, clients end up
  293. in HRESULT 0xC004F038 "The count reported by your Key Management
  294. Service (KMS) is insufficient. Please contact your system admin-
  295. istrator". You may use vlmcs(1) or another KMS client emulator
  296. to "charge" vlmcsd(8). Setting this parameter to TRUE does not
  297. improve emulator detection prevention. It's primary purpose is
  298. to help developers of KMS clients to test "charging" a KMS
  299. server.
  300. ActivationInterval
  301. This is the same as specifying -A on the command line. See vlm-
  302. csd(8) for details. The default is 2 hours. Example: Activation-
  303. Interval = 1h
  304. RenewalInterval
  305. This is the same as specifying -R on the command line. See vlm-
  306. csd(8) for details. The default is 7 days. Example: RenewalIn-
  307. terval = 3d. Please note that the KMS client decides itself when
  308. to renew activation. Even though vlmcsd sends the renewal inter-
  309. val you specify, it is no more than some kind of recommendation
  310. to the client. Older KMS clients did follow the recommendation
  311. from a KMS server or emulator. Newer clients do not.
  312. User Run vlmcsd as another, preferrably less privileged, user. The
  313. argument can be a user name or a numeric user id. You must have
  314. the required privileges (capabilities on Linux) to change the
  315. security context of a process without providing any credentials
  316. (a password in most cases). On most unixoid OSses 'root' is the
  317. only user who has these privileges in the default configuration.
  318. This setting is not available in the native Windows version of
  319. vlmcsd. See -u in vlmcsd(8). This setting cannot be changed on
  320. the fly by sending SIGHUP to vlmcsd.
  321. Group Run vlmcsd as another, preferrably less privileged, group. The
  322. argument can be a group name or a numeric group id. You must
  323. have the required privileges (capabilities on Linux) to change
  324. the security context of a process without providing any creden-
  325. tials (a password in most cases). On most unixoid OSses 'root'
  326. is the only user who has these privileges in the default config-
  327. uration. This setting is not available in the native Windows
  328. version of vlmcsd. See -g in vlmcsd(8). This setting cannot be
  329. changed on the fly by sending SIGHUP to vlmcsd.
  330. Windows
  331. The argument has the form ePID [ / HwId ]. Always use ePID and
  332. HwId for Windows activations. If specified, RandomizationLevel
  333. for Windows activitations will be ignored.
  334. Office2010
  335. The argument has the form ePID [ / HwId ]. Always use ePID and
  336. HwId for Office 2010 activations. If specified, Randomization-
  337. Level for Office 2010 activitations will be ignored.
  338. Office2013
  339. The argument has the form ePID [ / HwId ]. Always use ePID and
  340. HwId for Office 2013 activations. If specified, Randomization-
  341. Level for Office 2013 activitations will be ignored.
  342. Office2016
  343. The argument has the form ePID [ / HwId ]. Always use ePID and
  344. HwId for Office 2016 activations. If specified, Randomization-
  345. Level for Office 2016 activitations will be ignored.
  346. WinChinaGov
  347. The argument has the form ePID [ / HwId ]. Always use ePID and
  348. HwId for China Government Editions of Windows (Enterprise G/GN).
  349. If specified, RandomizationLevel for Windows China Government
  350. activitations will be ignored.
  351. VALID EPIDS
  352. The ePID is currently a comment only. You can specify any string up to
  353. 63 bytes. In Windows 7 Microsoft has blacklisted few ( < 10 ) ePIDs
  354. that were used in KMSv5 versions of the "Ratiborus Virtual Machine".
  355. Microsoft has given up on blacklisting when KMS emulators appeared in
  356. the wild.
  357. Even if you can use "Activated by cool hacker guys" as an ePID, you may
  358. wish to use ePIDs that cannot be detected as non-MS ePIDs. If you don't
  359. know how these "valid" ePIDs look like exactly, do not use GUIDS in
  360. vlmcsd.ini. vlmcsd provides internal mechanisms to generate valid
  361. ePIDs.
  362. If you use non-ASCII characters in your ePID (you shouldn't do anyway),
  363. these must be in UTF-8 format. This is especially important when you
  364. run vlmcsd on Windows or cygwin because UTF-8 is not the default encod-
  365. ing for most editors.
  366. If you are specifying an optional HWID it follows the same syntax as in
  367. the -H option in vlmcsd(8) ecxept that you must not enclose a HWID in
  368. quotes even if it contains spaces.
  369. FILES
  370. vlmcsd.ini(5)
  371. AUTHOR
  372. vlmcsd(8) was written by crony12, Hotbird64 and vityan666. With contri-
  373. butions from DougQaid.
  374. CREDITS
  375. Thanks to CODYQX4, deagles, eIcn, mikmik38, nosferati87, qad, Rati-
  376. borus, ...
  377. SEE ALSO
  378. vlmcsd(8), vlmcsd(7), vlmcs(1), vlmcsdmulti(1)
  379. Hotbird64 May 2017 VLMCSD.INI(5)