vlmcsd.ini.5.dos.txt 23 KB

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