vlmcsd-svn1085-2016-10-21-Hotbird64

GNUmakefile

@@ -189,6 +189,7 @@ help:
 	@echo "Useful CFLAGS to save memory when running $(BASE_PROGRAM_NAME) on very small embedded devices (finer control than FEATURES=)"
 	@echo "    -DNO_EXTENDED_PRODUCT_LIST   Don't compile the detailed product list."
 	@echo "    -DNO_BASIC_PRODUCT_LIST      Don't compile the basic product list."
+	@echo "    -DNO_STRICT_MODES            Don't support enhanced emulator detection prevention."
 	@echo "    -DNO_VERBOSE_LOG             Don't support verbose logging. Removes -v option."
 	@echo "    -DNO_LOG                     Don't add support for logging. Implies -DNO_VERBOSE_LOG -DNO_EXTENDED_PRODUCT_LIST and -DNO_BASIC_PRODUCT_LIST."
 	@echo "    -DNO_RANDOM_EPID             Don't support random ePIDs."
@@ -199,6 +200,8 @@ help:
 	@echo "    -DNO_CUSTOM_INTERVALS        Don't support custom intervals for retry and refresh activation. Removes -A and -R options."
 	@echo "    -DNO_FREEBIND                Don't support binding to foreign IP addresses. Removes -F0 and -F1 options. Only affects FreeBSD and Linux."
 	@echo "    -DNO_SOCKETS                 Don't support standalone operation. Requires an internet superserver to start $(BASE_PROGRAM_NAME)."
+	@echo "    -DSIMPLE_SOCKETS             Don't support listening on explicit IP addresses. Always listens on all IP addresses."
+	@echo "    -DSIMPLE_RPC                 Don't support RPC with NDR64 and BTFN in $(BASE_PROGRAM_NAME) (but do in $(BASE_CLIENT_NAME)). Makes emulator detection easy."
 	@echo "    -DNO_CL_PIDS                 Don't support specifying ePIDs and HwId from the command line in $(BASE_PROGRAM_NAME)."
 	@echo "    -DNO_LIMIT                   Don't support limiting concurrent clients in $(BASE_PROGRAM_NAME)."
 	@echo "    -DNO_SIGHUP                  Don't support SIGHUP handling in $(BASE_PROGRAM_NAME)."

VisualStudio/vlmcs/vlmcs.vcxproj

@@ -177,6 +177,7 @@
       <RuntimeTypeInfo>false</RuntimeTypeInfo>
       <OpenMPSupport>false</OpenMPSupport>
       <AdditionalOptions>$(ExternalCompilerOptions) %(AdditionalOptions)</AdditionalOptions>
+      <OmitFramePointers>true</OmitFramePointers>
     </ClCompile>
     <Link>
       <EnableCOMDATFolding>true</EnableCOMDATFolding>

VisualStudio/vlmcsd.sln

@@ -11,9 +11,9 @@ Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "vlmcsdmulti-Windows", "vlmc
 EndProject
 Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "libkms-Windows", "libkms\libkms.vcxproj", "{2A0FC04D-C3C0-43E2-8812-53AE901C5395}"
 EndProject
-Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "vlmcsd-gcc5", "..\vlmcsd-linux-remote.vcxproj", "{CC2FBE0B-B9DF-4306-88A1-20706BBD2B0C}"
+Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "vlmcsd-gcc5", "..\src\vlmcsd-linux-remote.vcxproj", "{CC2FBE0B-B9DF-4306-88A1-20706BBD2B0C}"
 EndProject
-Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "vlmcs-gcc5", "..\vlmcs-linux-remote.vcxproj", "{1ED83566-8AE1-4EE8-9B62-37188A7AC7CA}"
+Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "vlmcs-gcc5", "..\src\vlmcs-linux-remote.vcxproj", "{1ED83566-8AE1-4EE8-9B62-37188A7AC7CA}"
 EndProject
 Global
 	GlobalSection(SolutionConfigurationPlatforms) = preSolution

etc/vlmcsd.ini

@@ -82,6 +82,14 @@
 # Command line: -v and -q
 ;LogVerbose = true
 
+# Whitelist known products
+# Command line: -K0, -K1, -K2, -K3
+;WhiteListingLevel = 0
+
+# Check that the client time is within +/- 4 hours of the system time
+# Command Line: -c0, -c1
+;CheckClientTime = false
+
 # Set activation interval to 2 hours
 # Command line: -A
 ;ActivationInterval = 2h

hotbird64-mass-build/make_dragonfly

@@ -19,7 +19,7 @@ CF45="-static-libgcc -pipe -fno-common -fno-exceptions -fno-stack-protector -fno
 CFCLANG="-pipe -fno-common -fno-exceptions -fno-stack-protector -fno-unwind-tables -fno-asynchronous-unwind-tables -fmerge-all-constants"
 LF="-Wl,-z,norelro -Wl,--hash-style=sysv -Wl,--build-id=none"
 LFCLANG="-Wl,-z,norelro -Wl,--hash-style=sysv"
-export CC=gcc5
+export CC=gcc6
 
 gmake $MAKEFLAGS MULTI_NAME=$BINDIR/vlmcsdmulti-DragonFly-x64 PROGRAM_NAME=$BINDIR/vlmcsd-DragonFly-x64 CLIENT_NAME=$BINDIR/vlmcs-DragonFly-x64 CFLAGS="$CF" LDFLAGS="$LF" allmulti
 

man/vlmcs.1

@@ -1,5 +1,5 @@
 .mso www.tmac
-.TH VLMCS 1 "May 2016" "Hotbird64" "KMS Activation Manual"
+.TH VLMCS 1 "October 2016" "Hotbird64" "KMS Activation Manual"
 .LO 1
 
 .SH NAME
@@ -76,7 +76,7 @@ to specify applications that are not listed with \fB-x\fR. The
 option is used as a shortcut for the most common applications.
 
 .IP "\fB-K\fR \fIprotocol-version\fR"
-Force a specific version of the KMS protocol. Valid versions are 4.0, 5.0 and 6.0. The default is to select a suitable version according to the \fIapplication\fR selected. You may use \fB-K\fR to send an incorrect protocol version to the KMS server and see how it behaves. Genuine KMS servers return HRESULT 0x8007000D if the KMS protocol is not 4.0, 5.0 or 6.0. Emulators should do the same. When sending a request with an incorrect protocol number, vlmcs ignores the minor protocol number (e.g. sends a v4 request for version 4.1). If the major version number is less then 4, it sends a v4 request. If the major version is greater then 6, is sends a v6 request. In any case the \fIprotocol-version\fR as specified by \fB-K\fR is put in the version fields of the request.
+Force a specific version of the KMS protocol. Valid versions are 4.0, 5.0 and 6.0. The default is to select a suitable version according to the \fIapplication\fR selected. You may use \fB-K\fR to send an incorrect protocol version to the KMS server and see how it behaves. Genuine KMS servers return HRESULT 0x8007000D if the KMS protocol is not 4.0, 5.0 or 6.0. Emulators should do the same. When sending a request with an incorrect protocol number, vlmcs ignores the minor protocol number (e.g. sends a v4 request for version 4.1). If the major version number is less then 4, it sends a v4 request. If the major version is greater then 6, it sends a v6 request. In any case the \fIprotocol-version\fR as specified by \fB-K\fR is put in the version fields of the request.
 
 .IP "\fB-4\fR, \fB-5\fR and \fB-6"
 Force version 4, 5 or 6 of the KMS protocol. These options are actually shortcuts of \fB-K 4.0\fR, \fB-K 5.0\fR and \fB-K 6.0\fR.

man/vlmcs.1.dos.txt

@@ -90,7 +90,7 @@ OPTIONS
               same. When sending a request with an incorrect protocol  number,
               vlmcs ignores the minor protocol number (e.g. sends a v4 request
               for version 4.1). If the major version number is less then 4, it
-              sends  a  v4 request. If the major version is greater then 6, is
+              sends  a  v4 request. If the major version is greater then 6, it
               sends a v6 request. In any case the protocol-version  as  speci‐
               fied by -K is put in the version fields of the request.
 
@@ -323,4 +323,4 @@ SEE ALSO
 
 
 
-Hotbird64                          May 2016                           VLMCS(1)
+Hotbird64                        October 2016                         VLMCS(1)

man/vlmcs.1.html

@@ -1,5 +1,5 @@
 <!-- Creator     : groff version 1.22.3 -->
-<!-- CreationDate: Tue Oct 11 21:34:50 2016 -->
+<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
 "http://www.w3.org/TR/html4/loose.dtd">
 <html>
@@ -39,7 +39,7 @@
 </h2>
 
 
-<p style="margin-left:11%; margin-top: 1em">vlmcs &minus; a
+<p style="margin-left:11%; margin-top: 1em">vlmcs - a
 client for testing and/or charging KMS servers</p>
 
 <h2>SYNOPSIS
@@ -197,7 +197,7 @@ the same. When sending a request with an incorrect protocol
 number, vlmcs ignores the minor protocol number (e.g. sends
 a v4 request for version 4.1). If the major version number
 is less then 4, it sends a v4 request. If the major version
-is greater then 6, is sends a v6 request. In any case the
+is greater then 6, it sends a v6 request. In any case the
 <i>protocol-version</i> as specified by <b>-K</b> is put in
 the version fields of the request.</p>
 
@@ -292,7 +292,7 @@ ExtendedProductList).</p>
 <p style="margin-left:22%;">Send <i>requests</i> requests
 to the server. The default is to send at least one request
 and enough subsequent requests that the server is fully
-charged afterwards for the <i>application&minus;guid</i> you
+charged afterwards for the <i>application-guid</i> you
 selected (explicitly with <b>-a</b> or implicitly by using
 <b>-l</b>).</p>
 
@@ -384,7 +384,7 @@ what was specified with <b>-r</b>. This option can be used
 to &quot;overcharge&quot; a Microsoft KMS server.</p>
 
 
-<p style="margin-left:11%;"><b>&minus;t&nbsp;</b><i>status</i></p>
+<p style="margin-left:11%;"><b>-t&nbsp;</b><i>status</i></p>
 
 <p style="margin-left:22%;">Reports a specific license
 status to the KMS server. <i>status</i> is a number that can

man/vlmcs.1.unix.txt

@@ -90,7 +90,7 @@ OPTIONS
               same. When sending a request with an incorrect protocol  number,
               vlmcs ignores the minor protocol number (e.g. sends a v4 request
               for version 4.1). If the major version number is less then 4, it
-              sends  a  v4 request. If the major version is greater then 6, is
+              sends  a  v4 request. If the major version is greater then 6, it
               sends a v6 request. In any case the protocol-version  as  speci‐
               fied by -K is put in the version fields of the request.
 
@@ -323,4 +323,4 @@ SEE ALSO
 
 
 
-Hotbird64                          May 2016                           VLMCS(1)
+Hotbird64                        October 2016                         VLMCS(1)

man/vlmcsd-floppy.7.html

@@ -1,5 +1,5 @@
 <!-- Creator     : groff version 1.22.3 -->
-<!-- CreationDate: Tue Oct 11 21:34:50 2016 -->
+<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
 "http://www.w3.org/TR/html4/loose.dtd">
 <html>
@@ -42,9 +42,8 @@
 </h2>
 
 
-<p style="margin-left:11%; margin-top: 1em">floppy144.vfd
-&minus; a bootable floppy disk with Linux and
-<b>vlmcsd</b>(8)</p>
+<p style="margin-left:11%; margin-top: 1em">floppy144.vfd -
+a bootable floppy disk with Linux and <b>vlmcsd</b>(8)</p>
 
 <h2>DESCRIPTION
 <a name="DESCRIPTION"></a>
@@ -549,9 +548,9 @@ addresses and all user names and passwords.</p>
 <p style="margin-left:11%; margin-top: 1em"><b>Logging into
 the system</b> <br>
 There are 5 local logins provided on /dev/tty2 to /dev/tty6.
-To switch to these logins, simply press ALT&minus;F2 to
-ALT&minus;F6. To return to the console on /dev/tty1, press
-ALT&minus;F1. If <b>inetd</b>(8) is running you can also use
+To switch to these logins, simply press ALT-F2 to ALT-F6. To
+return to the console on /dev/tty1, press ALT-F1. If
+<b>inetd</b>(8) is running you can also use
 <b>telnet</b>(1). This allows you use a terminal program
 (e.g. putty) that can utilize your keyboard layout, can be
 resized and has full UTF-8 support. The local terminals
@@ -571,11 +570,11 @@ editor of your choice and transfer them back to the
 
 <p style="margin-left:11%; margin-top: 1em"><b>The menu
 system</b> <br>
-You&rsquo;ll find a menu system on /dev/tty8 (press
-ALT&minus;F8 to see it). It allows you performing some
-administrative tasks and to view various system information.
-It is mainly for users that do not have much experience with
-Unix commands. <b><br>
+You&rsquo;ll find a menu system on /dev/tty8 (press ALT-F8
+to see it). It allows you performing some administrative
+tasks and to view various system information. It is mainly
+for users that do not have much experience with Unix
+commands. <b><br>
 1) (Re)start vlmcsd</b></p>
 
 <p style="margin-left:22%;">Starts or restarts

man/vlmcsd.7.html

@@ -1,5 +1,5 @@
 <!-- Creator     : groff version 1.22.3 -->
-<!-- CreationDate: Tue Oct 11 21:34:50 2016 -->
+<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
 "http://www.w3.org/TR/html4/loose.dtd">
 <html>
@@ -35,7 +35,7 @@
 
 
 
-<p style="margin-left:11%; margin-top: 1em">vlmcsd&nbsp;&minus;&nbsp;a
+<p style="margin-left:11%; margin-top: 1em">vlmcsd&nbsp;-&nbsp;a
 guide to KMS activation using vlmcsd</p>
 
 <h2>SYNOPSIS
@@ -169,34 +169,29 @@ inofficial GVLKs that work with consumer-only versions of
 Windows. Here is a list:</p>
 
 
-<p style="margin-left:11%; margin-top: 1em">TX9XD&minus;98N7V&minus;6WMQ6&minus;BX7FG&minus;H8Q99
+<p style="margin-left:11%; margin-top: 1em">TX9XD-98N7V-6WMQ6-BX7FG-H8Q99
 - Windows 10 Home <br>
-3KHY7&minus;WNT83&minus;DGQKR&minus;F7HPR&minus;844BM -
-Windows 10 Home N <br>
-7HNRX&minus;D7KGG&minus;3K4RQ&minus;4WPJ4&minus;YTDFH -
-Windows 10 Home Single Language <br>
-PVMJN&minus;6DFY6&minus;9CCP6&minus;7BKTT&minus;D3WVR -
-Windows 10 Home Country Specific <br>
-789NJ&minus;TQK6T&minus;6XTH8&minus;J39CJ&minus;J8D3P -
-Windows 8.1 Professional with Media Center <br>
-M9Q9P&minus;WNJJT&minus;6PXPY&minus;DWX8H&minus;6XWKK -
-Windows 8.1 Core <br>
-7B9N3&minus;D94CG&minus;YTVHR&minus;QBPX3&minus;RJP64 -
-Windows 8.1 Core N <br>
-BB6NG&minus;PQ82V&minus;VRDPW&minus;8XVD2&minus;V8P66 -
-Windows 8.1 Core Single Language <br>
-NCTT7&minus;2RGK8&minus;WMHRF&minus;RY7YQ&minus;JTXG3 -
-Windows 8.1 Core Country Specific <br>
-GNBB8&minus;YVD74&minus;QJHX6&minus;27H4K&minus;8QHDG -
-Windows 8 Professional with Media Center <br>
-BN3D2&minus;R7TKB&minus;3YPBD&minus;8DRP2&minus;27GG4 -
-Windows 8 Core <br>
-8N2M2&minus;HWPGY&minus;7PGT9&minus;HGDD8&minus;GVGGY -
-Windows 8 Core N <br>
-2WN2H&minus;YGCQR&minus;KFX6K&minus;CD6TF&minus;84YXQ -
-Windows 8 Core Single Language <br>
-4K36P&minus;JN4VD&minus;GDC6V&minus;KDT89&minus;DYFKP -
-Windows 8 Core Country Specific</p>
+3KHY7-WNT83-DGQKR-F7HPR-844BM - Windows 10 Home N <br>
+7HNRX-D7KGG-3K4RQ-4WPJ4-YTDFH - Windows 10 Home Single
+Language <br>
+PVMJN-6DFY6-9CCP6-7BKTT-D3WVR - Windows 10 Home Country
+Specific <br>
+789NJ-TQK6T-6XTH8-J39CJ-J8D3P - Windows 8.1 Professional
+with Media Center <br>
+M9Q9P-WNJJT-6PXPY-DWX8H-6XWKK - Windows 8.1 Core <br>
+7B9N3-D94CG-YTVHR-QBPX3-RJP64 - Windows 8.1 Core N <br>
+BB6NG-PQ82V-VRDPW-8XVD2-V8P66 - Windows 8.1 Core Single
+Language <br>
+NCTT7-2RGK8-WMHRF-RY7YQ-JTXG3 - Windows 8.1 Core Country
+Specific <br>
+GNBB8-YVD74-QJHX6-27H4K-8QHDG - Windows 8 Professional with
+Media Center <br>
+BN3D2-R7TKB-3YPBD-8DRP2-27GG4 - Windows 8 Core <br>
+8N2M2-HWPGY-7PGT9-HGDD8-GVGGY - Windows 8 Core N <br>
+2WN2H-YGCQR-KFX6K-CD6TF-84YXQ - Windows 8 Core Single
+Language <br>
+4K36P-JN4VD-GDC6V-KDT89-DYFKP - Windows 8 Core Country
+Specific</p>
 
 <p style="margin-left:11%; margin-top: 1em">The above keys
 require activation renewal every 45 days (Win 8.1) or 30
@@ -240,9 +235,9 @@ turned out to be non-working, you can use
 Examples</b></p>
 
 <p style="margin-left:22%;">slmgr&nbsp;/ipk
-GCRJD&minus;8NW9H&minus;F2CDX&minus;CCM8D&minus;9D6T9 <br>
+GCRJD-8NW9H-F2CDX-CCM8D-9D6T9 <br>
 cscript
-ospp.vbs&nbsp;/inpkey:YC7DK&minus;G2NP3&minus;2QQC3&minus;J6H88&minus;GVGXT</p>
+ospp.vbs&nbsp;/inpkey:YC7DK-G2NP3-2QQC3-J6H88-GVGXT</p>
 
 <p style="margin-left:11%; margin-top: 1em"><b>Why
 doesn&rsquo;t Office accpet a GVLK?</b> <br>
@@ -306,7 +301,7 @@ automatically. This may take a while. <br>
 You may type</p>
 
 <p style="margin-left:22%;">slmgr&nbsp;/ato <br>
-&minus;or&minus; <br>
+-or- <br>
 cscript ospp.vbs&nbsp;/act</p>
 
 <p style="margin-left:11%; margin-top: 1em">at any time to
@@ -325,8 +320,8 @@ like this:</p>
 <p style="margin-left:22%; margin-top: 1em">Connecting to
 127.0.0.1:1688 ... successful <br>
 
-Sending&nbsp;activation&nbsp;request&nbsp;(KMS&nbsp;V4)&nbsp;1&nbsp;of&nbsp;1&nbsp;&minus;&gt;
-06401&minus;00206&minus;296&minus;206344&minus;03&minus;5179&minus;9600.0000&minus;3432013</p>
+Sending&nbsp;activation&nbsp;request&nbsp;(KMS&nbsp;V4)&nbsp;1&nbsp;of&nbsp;1&nbsp;-&gt;
+06401-00206-296-206344-03-5179-9600.0000-3432013</p>
 
 <p style="margin-left:11%; margin-top: 1em">If anything
 goes wrong, you&rsquo;ll see an error message. Next try

man/vlmcsd.8

@@ -1,5 +1,5 @@
 .mso www.tmac
-.TH VLMCSD 8 "September 2016" "Hotbird64" "KMS Activation Manual"
+.TH VLMCSD 8 "October 2016" "Hotbird64" "KMS Activation Manual"
 .LO 8
 
 .SH NAME
@@ -184,6 +184,25 @@ for a list of valid \fILCID\fRs. Please note that some of them are not recognize
 
 Most other KMS emulators use a fixed \fILCID\fR of 1033 (English - US). To achive the same behavior in vlmcsd use \fB-C 1033\fR.
 
+.IP "\fB-K0\fR, \fB-K1\fR, \fB-K2\fR and \fB-K3\fR"
+Sets the whitelisting level to determine which products vlmcsd activates or refuses. The default is \fB-K0\fR.
+
+.RS 12
+\fB-K0\fR: activate all products with an unknown, retail or beta/preview KMS ID.
+.br
+\fB-K1\fR: activate products with a retail or beta/preview KMS ID but refuse to activate products with an unknown KMS ID.
+.br
+\fB-K2\fR: activate products with an unknown KMS ID but refuse products with a retail or beta/preview KMS ID.
+.br
+\fB-K3\fR: activate only products with a known volume license RTM KMS ID and refuse all others.
+.RE
+
+.IP ""
+The SKU ID is not checked. Like a genuine KMS server vlmcsd activates a product that has a random or unknown SKU ID. If you select \fB-K1\fR or \fB-K3\fR, vlmcsd also checks the Application ID for correctness. If Microsoft introduces a new KMS ID for a new product, you cannot activate it if you used \fB-K1\fR or \fB-K3\fR until a new version of vlmcsd is available.
+
+.IP "\fB-c0\fR and \fB-c1\fR"
+\fB-c1\fR causes vlmcsd to check if the client time differs no more than four hours from the system time. \fB-c0\fR (the default) disables this check. \fB-c1\fR is useful to prevent emulator detection. A client that tries to detect an emulator could simply send two subsequent request with two time stamps that differ more than four hours from each other. If both requests succeed, the server is an emulator. If you specify \fB-c1\fR on a system with no reliable time source, activations will fail. It is ok to set the correct system time after you started vlmcsd.
+
 .IP "\fB-R\fR \fIrenewal-interval\fR"
 Instructs clients to renew activation every \fIrenewal-interval\fR. The \fIrenewal-interval\fR is a number optionally immediately followed by a letter indicating the unit. Valid unit letters are s (seconds), m (minutes), h (hours), d (days) and w (weeks). If you do not specify a letter, minutes is assumed.
 
@@ -274,8 +293,6 @@ Installs \fBvlmcsd\fR as a Windows service with low privileges and logs everythi
 An ePID specified in an ini file must not contain spaces.
 
 .SH INTENTIONAL BUGS
-vlmcsd activates non-VL (retail) and beta/preview versions of Windows.
-.br
 vlmcsd always reports enough active clients to satisfy the N count policy of the request.
 
 .SH AUTHOR

man/vlmcsd.8.dos.txt

@@ -415,6 +415,40 @@ OPTIONS
               US). To achive the same behavior in vlmcsd use -C 1033.
 
 
+       -K0, -K1, -K2 and -K3
+              Sets the whitelisting level to determine which  products  vlmcsd
+              activates or refuses. The default is -K0.
+
+                   -K0:  activate  all  products  with  an  unknown, retail or
+                   beta/preview KMS ID.
+                   -K1: activate products with a retail or beta/preview KMS ID
+                   but refuse to activate products with an unknown KMS ID.
+                   -K2:  activate  products  with an unknown KMS ID but refuse
+                   products with a retail or beta/preview KMS ID.
+                   -K3: activate only products with a known volume license RTM
+                   KMS ID and refuse all others.
+
+
+              The  SKU  ID  is  not  checked. Like a genuine KMS server vlmcsd
+              activates a product that has a random or unknown SKU ID. If  you
+              select  -K1  or  -K3,  vlmcsd also checks the Application ID for
+              correctness. If Microsoft introduces a new  KMS  ID  for  a  new
+              product,  you  cannot activate it if you used -K1 or -K3 until a
+              new version of vlmcsd is available.
+
+
+       -c0 and -c1
+              -c1 causes vlmcsd to check if the client time  differs  no  more
+              than four hours from the system time. -c0 (the default) disables
+              this check. -c1 is  useful  to  prevent  emulator  detection.  A
+              client  that  tries  to detect an emulator could simply send two
+              subsequent request with two time stamps that  differ  more  than
+              four hours from each other. If both requests succeed, the server
+              is an emulator. If you specify -c1 on a system with no  reliable
+              time  source, activations will fail. It is ok to set the correct
+              system time after you started vlmcsd.
+
+
        -R renewal-interval
               Instructs clients to renew  activation  every  renewal-interval.
               The renewal-interval is a number optionally immediately followed
@@ -592,7 +626,6 @@ BUGS
 
 
 INTENTIONAL BUGS
-       vlmcsd activates non-VL (retail) and beta/preview versions of Windows.
        vlmcsd always reports enough active clients to satisfy the N count pol‐
        icy of the request.
 
@@ -612,4 +645,4 @@ SEE ALSO
 
 
 
-Hotbird64                       September 2016                       VLMCSD(8)
+Hotbird64                        October 2016                        VLMCSD(8)

man/vlmcsd.8.html

@@ -1,5 +1,5 @@
 <!-- Creator     : groff version 1.22.3 -->
-<!-- CreationDate: Tue Oct 11 21:34:50 2016 -->
+<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
 "http://www.w3.org/TR/html4/loose.dtd">
 <html>
@@ -43,8 +43,8 @@
 </h2>
 
 
-<p style="margin-left:11%; margin-top: 1em">vlmcsd &minus;
-a fully Microsoft compatible KMS server</p>
+<p style="margin-left:11%; margin-top: 1em">vlmcsd - a
+fully Microsoft compatible KMS server</p>
 
 <h2>SYNOPSIS
 <a name="SYNOPSIS"></a>
@@ -619,6 +619,54 @@ them are not recognized by .NET Framework 4.0.</p>
 emulators use a fixed <i>LCID</i> of 1033 (English - US). To
 achive the same behavior in vlmcsd use <b>-C 1033</b>.</p>
 
+<p style="margin-left:11%;"><b>-K0</b>, <b>-K1</b>,
+<b>-K2</b> and <b>-K3</b></p>
+
+<p style="margin-left:22%;">Sets the whitelisting level to
+determine which products vlmcsd activates or refuses. The
+default is <b>-K0</b>.</p>
+
+<p style="margin-left:29%; margin-top: 1em"><b>-K0</b>:
+activate all products with an unknown, retail or
+beta/preview KMS ID. <b><br>
+-K1</b>: activate products with a retail or beta/preview KMS
+ID but refuse to activate products with an unknown KMS ID.
+<b><br>
+-K2</b>: activate products with an unknown KMS ID but refuse
+products with a retail or beta/preview KMS ID. <b><br>
+-K3</b>: activate only products with a known volume license
+RTM KMS ID and refuse all others.</p>
+
+<table width="100%" border="0" rules="none" frame="void"
+       cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="22%"></td>
+<td width="78%">
+
+
+<p>The SKU ID is not checked. Like a genuine KMS server
+vlmcsd activates a product that has a random or unknown SKU
+ID. If you select <b>-K1</b> or <b>-K3</b>, vlmcsd also
+checks the Application ID for correctness. If Microsoft
+introduces a new KMS ID for a new product, you cannot
+activate it if you used <b>-K1</b> or <b>-K3</b> until a new
+version of vlmcsd is available.</p></td></tr>
+</table>
+
+<p style="margin-left:11%;"><b>-c0</b> and <b>-c1</b></p>
+
+<p style="margin-left:22%;"><b>-c1</b> causes vlmcsd to
+check if the client time differs no more than four hours
+from the system time. <b>-c0</b> (the default) disables this
+check. <b>-c1</b> is useful to prevent emulator detection. A
+client that tries to detect an emulator could simply send
+two subsequent request with two time stamps that differ more
+than four hours from each other. If both requests succeed,
+the server is an emulator. If you specify <b>-c1</b> on a
+system with no reliable time source, activations will fail.
+It is ok to set the correct system time after you started
+vlmcsd.</p>
+
 <p style="margin-left:11%;"><b>-R</b>
 <i>renewal-interval</i></p>
 
@@ -736,8 +784,8 @@ directory.</p>
 convenience you can use the special username &quot;/l&quot;
 as a shortcut for &quot;NT AUTHORITY\LocalService&quot; and
 &quot;/n&quot; for &quot;NT AUTHORITY\NetworkService&quot;.
-&quot;vlmcsd&nbsp;&minus;s&nbsp;&minus;U&nbsp;/n&quot;
-installs the service to run as &quot;NT
+&quot;vlmcsd&nbsp;-s&nbsp;-U&nbsp;/n&quot; installs the
+service to run as &quot;NT
 AUTHORITY\NetworkService&quot;.</p>
 
 <p style="margin-left:11%;"><b>-W</b> <i>password</i></p>
@@ -928,11 +976,9 @@ specified in an ini file must not contain spaces.</p>
 </h2>
 
 
-<p style="margin-left:11%; margin-top: 1em">vlmcsd
-activates non-VL (retail) and beta/preview versions of
-Windows. <br>
-vlmcsd always reports enough active clients to satisfy the N
-count policy of the request.</p>
+<p style="margin-left:11%; margin-top: 1em">vlmcsd always
+reports enough active clients to satisfy the N count policy
+of the request.</p>
 
 <h2>AUTHOR
 <a name="AUTHOR"></a>

man/vlmcsd.8.unix.txt

@@ -415,6 +415,40 @@ OPTIONS
               US). To achive the same behavior in vlmcsd use -C 1033.
 
 
+       -K0, -K1, -K2 and -K3
+              Sets the whitelisting level to determine which  products  vlmcsd
+              activates or refuses. The default is -K0.
+
+                   -K0:  activate  all  products  with  an  unknown, retail or
+                   beta/preview KMS ID.
+                   -K1: activate products with a retail or beta/preview KMS ID
+                   but refuse to activate products with an unknown KMS ID.
+                   -K2:  activate  products  with an unknown KMS ID but refuse
+                   products with a retail or beta/preview KMS ID.
+                   -K3: activate only products with a known volume license RTM
+                   KMS ID and refuse all others.
+
+
+              The  SKU  ID  is  not  checked. Like a genuine KMS server vlmcsd
+              activates a product that has a random or unknown SKU ID. If  you
+              select  -K1  or  -K3,  vlmcsd also checks the Application ID for
+              correctness. If Microsoft introduces a new  KMS  ID  for  a  new
+              product,  you  cannot activate it if you used -K1 or -K3 until a
+              new version of vlmcsd is available.
+
+
+       -c0 and -c1
+              -c1 causes vlmcsd to check if the client time  differs  no  more
+              than four hours from the system time. -c0 (the default) disables
+              this check. -c1 is  useful  to  prevent  emulator  detection.  A
+              client  that  tries  to detect an emulator could simply send two
+              subsequent request with two time stamps that  differ  more  than
+              four hours from each other. If both requests succeed, the server
+              is an emulator. If you specify -c1 on a system with no  reliable
+              time  source, activations will fail. It is ok to set the correct
+              system time after you started vlmcsd.
+
+
        -R renewal-interval
               Instructs clients to renew  activation  every  renewal-interval.
               The renewal-interval is a number optionally immediately followed
@@ -592,7 +626,6 @@ BUGS
 
 
 INTENTIONAL BUGS
-       vlmcsd activates non-VL (retail) and beta/preview versions of Windows.
        vlmcsd always reports enough active clients to satisfy the N count pol‐
        icy of the request.
 
@@ -612,4 +645,4 @@ SEE ALSO
 
 
 
-Hotbird64                       September 2016                       VLMCSD(8)
+Hotbird64                        October 2016                        VLMCSD(8)

man/vlmcsd.ini.5

@@ -1,4 +1,4 @@
-.TH VLMCSD.INI 5 "September 2016" "Hotbird64" "KMS Activation Manual"
+.TH VLMCSD.INI 5 "October 2016" "Hotbird64" "KMS Activation Manual"
 .LO 8
 
 .SH NAME
@@ -99,6 +99,25 @@ Can be TRUE or FALSE. The default is TRUE. If set to FALSE, logging output does
 .IP "\fBLogVerbose\fR"
 Set this to either TRUE or FALSE. The default is FALSE. If set to TRUE, more details of each activation will be logged. You use \fB-v\fR and \fB-q\fR in the command line to control this setting. \fBLogVerbose\fR has an effect only if you specify a log file or redirect logging to \fBstdout\fR(3).
 
+.IP "\fBWhitelistingLevel\fR"
+Can be 0, 1, 2 or 3. The default is 0. Sets the whitelisting level to determine which products vlmcsd activates or refuses.
+
+.RS 12
+\fB0\fR: activate all products with an unknown, retail or beta/preview KMS ID.
+.br
+\fB1\fR: activate products with a retail or beta/preview KMS ID but refuse to activate products with an unknown KMS ID.
+.br
+\fB2\fR: activate products with an unknown KMS ID but refuse products with a retail or beta/preview KMS ID.
+.br
+\fB3\fR: activate only products with a known volume license RTM KMS ID and refuse all others.
+.RE
+
+.IP ""
+The SKU ID is not checked. Like a genuine KMS server vlmcsd activates a product that has a random or unknown SKU ID. If you select \fB1\fR or \fB3\fR, vlmcsd also checks the Application ID for correctness. If Microsoft introduces a new KMS ID for a new product, you cannot activate it if you used \fB1\fR or \fB3\fR until a new version of vlmcsd is available.
+
+.IP "\fBCheckClientTime\fR"
+Can be TRUE or FALSE. The default is FALSE. If you set this to TRUE \fBvlmcsd\fR(8) checks if the client time differs no more than four hours from the system time. This is useful to prevent emulator detection. A client that tries to detect an emulator could simply send two subsequent request with two time stamps that differ more than four hours from each other. If both requests succeed, the server is an emulator. If you set this to TRUE on a system with no reliable time source, activations will fail. It is ok to set the correct system time after you started \fBvlmcsd\fR(8).
+
 .IP "\fBActivationInterval\fR"
 This is the same as specifying \fB-A\fR on the command line. See \fBvlmcsd\fR(8) for details. The default is 2 hours. Example: ActivationInterval = 1h
 

man/vlmcsd.ini.5.dos.txt

@@ -208,88 +208,123 @@ KEYWORDS
               logging to stdout(3).
 
 
+       WhitelistingLevel
+              Can  be  0,  1,  2 or 3. The default is 0. Sets the whitelisting
+              level to determine which products vlmcsd activates or refuses.
+
+                   0:  activate  all  products  with  an  unknown,  retail  or
+                   beta/preview KMS ID.
+                   1:  activate  products with a retail or beta/preview KMS ID
+                   but refuse to activate products with an unknown KMS ID.
+                   2: activate products with an  unknown  KMS  ID  but  refuse
+                   products with a retail or beta/preview KMS ID.
+                   3:  activate  only products with a known volume license RTM
+                   KMS ID and refuse all others.
+
+
+              The SKU ID is not checked. Like  a  genuine  KMS  server  vlmcsd
+              activates  a product that has a random or unknown SKU ID. If you
+              select 1 or 3, vlmcsd also checks the Application  ID  for  cor‐
+              rectness.  If  Microsoft introduces a new KMS ID for a new prod‐
+              uct, you cannot activate it if you used 1 or 3 until a new  ver‐
+              sion of vlmcsd is available.
+
+
+       CheckClientTime
+              Can  be  TRUE or FALSE. The default is FALSE. If you set this to
+              TRUE vlmcsd(8) checks if the client time differs  no  more  than
+              four  hours from the system time. This is useful to prevent emu‐
+              lator detection. A client that tries to detect an emulator could
+              simply  send  two  subsequent  request with two time stamps that
+              differ more than four hours from each other.  If  both  requests
+              succeed, the server is an emulator. If you set this to TRUE on a
+              system with no reliable time source, activations will  fail.  It
+              is  ok  to  set  the  correct system time after you started vlm‐
+              csd(8).
+
+
        ActivationInterval
-              This  is the same as specifying -A on the command line. See vlm‐
+              This is the same as specifying -A on the command line. See  vlm‐
               csd(8) for details. The default is 2 hours. Example: Activation‐
               Interval = 1h
 
 
        RenewalInterval
-              This  is the same as specifying -R on the command line. See vlm‐
-              csd(8) for details. The default is 7 days.  Example:  RenewalIn‐
+              This is the same as specifying -R on the command line. See  vlm‐
+              csd(8)  for  details. The default is 7 days. Example: RenewalIn‐
               terval = 3d. Please note that the KMS client decides itself when
               to renew activation. Even though vlmcsd sends the renewal inter‐
-              val  you specify, it is no more than some kind of recommendation
-              to the client. Older KMS clients did follow  the  recommendation
+              val you specify, it is no more than some kind of  recommendation
+              to  the  client. Older KMS clients did follow the recommendation
               from a KMS server or emulator. Newer clients do not.
 
 
-       User   Run  vlmcsd  as  another, preferrably less privileged, user. The
-              argument can be a user name or a numeric user id. You must  have
-              the  required  privileges  (capabilities on Linux) to change the
-              security context of a process without providing any  credentials
-              (a  password in most cases). On most unixoid OSses 'root' is the
+       User   Run vlmcsd as another, preferrably less  privileged,  user.  The
+              argument  can be a user name or a numeric user id. You must have
+              the required privileges (capabilities on Linux)  to  change  the
+              security  context of a process without providing any credentials
+              (a password in most cases). On most unixoid OSses 'root' is  the
               only user who has these privileges in the default configuration.
-              This  setting  is not available in the native Windows version of
-              vlmcsd. See -u in vlmcsd(8). This setting cannot be  changed  on
+              This setting is not available in the native Windows  version  of
+              vlmcsd.  See  -u in vlmcsd(8). This setting cannot be changed on
               the fly by sending SIGHUP to vlmcsd.
 
 
-       Group  Run  vlmcsd  as another, preferrably less privileged, group. The
-              argument can be a group name or a numeric  group  id.  You  must
-              have  the  required privileges (capabilities on Linux) to change
-              the security context of a process without providing any  creden‐
-              tials  (a  password in most cases). On most unixoid OSses 'root'
+       Group  Run vlmcsd as another, preferrably less privileged,  group.  The
+              argument  can  be  a  group name or a numeric group id. You must
+              have the required privileges (capabilities on Linux)  to  change
+              the  security context of a process without providing any creden‐
+              tials (a password in most cases). On most unixoid  OSses  'root'
               is the only user who has these privileges in the default config‐
-              uration.  This  setting  is  not available in the native Windows
-              version of vlmcsd. See -g in vlmcsd(8). This setting  cannot  be
+              uration. This setting is not available  in  the  native  Windows
+              version  of  vlmcsd. See -g in vlmcsd(8). This setting cannot be
               changed on the fly by sending SIGHUP to vlmcsd.
 
 
        Windows
-              The  argument  has the form ePID [ / HwId ]. Always use ePID and
-              HwId for Windows activations. If  specified,  RandomizationLevel
+              The argument has the form ePID [ / HwId ]. Always use  ePID  and
+              HwId  for  Windows activations. If specified, RandomizationLevel
               for Windows activitations will be ignored.
 
 
        Office2010
-              The  argument  has the form ePID [ / HwId ]. Always use ePID and
-              HwId for Office 2010 activations. If  specified,  Randomization‐
+              The argument has the form ePID [ / HwId ]. Always use  ePID  and
+              HwId  for  Office 2010 activations. If specified, Randomization‐
               Level for Office 2010 activitations will be ignored.
 
 
        Office2013
-              The  argument  has the form ePID [ / HwId ]. Always use ePID and
-              HwId for Office 2013 activations. If  specified,  Randomization‐
+              The argument has the form ePID [ / HwId ]. Always use  ePID  and
+              HwId  for  Office 2013 activations. If specified, Randomization‐
               Level for Office 2013 activitations will be ignored.
 
 
        Office2016
-              The  argument  has the form ePID [ / HwId ]. Always use ePID and
-              HwId for Office 2016 activations. If  specified,  Randomization‐
+              The argument has the form ePID [ / HwId ]. Always use  ePID  and
+              HwId  for  Office 2016 activations. If specified, Randomization‐
               Level for Office 2016 activitations will be ignored.
 
 
 VALID EPIDS
-       The  ePID is currently a comment only. You can specify any string up to
-       63 bytes. In Windows 7 Microsoft has blacklisted few (  <  10  )  ePIDs
-       that  were  used  in KMSv5 versions of the "Ratiborus Virtual Machine".
-       Microsoft has given up on blacklisting when KMS emulators  appeared  in
+       The ePID is currently a comment only. You can specify any string up  to
+       63  bytes.  In  Windows  7 Microsoft has blacklisted few ( < 10 ) ePIDs
+       that were used in KMSv5 versions of the  "Ratiborus  Virtual  Machine".
+       Microsoft  has  given up on blacklisting when KMS emulators appeared in
        the wild.
 
        Even if you can use "Activated by cool hacker guys" as an ePID, you may
        wish to use ePIDs that cannot be detected as non-MS ePIDs. If you don't
-       know  how  these  "valid"  ePIDs look like exactly, do not use GUIDS in
-       vlmcsd.ini. vlmcsd  provides  internal  mechanisms  to  generate  valid
+       know how these "valid" ePIDs look like exactly, do  not  use  GUIDS  in
+       vlmcsd.ini.  vlmcsd  provides  internal  mechanisms  to  generate valid
        ePIDs.
 
        If you use non-ASCII characters in your ePID (you shouldn't do anyway),
-       these must be in UTF-8 format. This is especially  important  when  you
+       these  must  be  in UTF-8 format. This is especially important when you
        run vlmcsd on Windows or cygwin because UTF-8 is not the default encod‐
        ing for most editors.
 
        If you are specifying an optional HWID it follows the same syntax as in
-       the  -H  option in vlmcsd(8) ecxept that you must not enclose a HWID in
+       the -H option in vlmcsd(8) ecxept that you must not enclose a  HWID  in
        quotes even if it contains spaces.
 
 
@@ -303,7 +338,7 @@ AUTHOR
 
 
 CREDITS
-       Thanks  to  CODYQX4,  deagles,  eIcn, mikmik38, nosferati87, qad, Rati‐
+       Thanks to CODYQX4, deagles, eIcn,  mikmik38,  nosferati87,  qad,  Rati‐
        borus, ...
 
 
@@ -312,4 +347,4 @@ SEE ALSO
 
 
 
-Hotbird64                       September 2016                   VLMCSD.INI(5)
+Hotbird64                        October 2016                    VLMCSD.INI(5)

man/vlmcsd.ini.5.html

@@ -1,5 +1,5 @@
 <!-- Creator     : groff version 1.22.3 -->
-<!-- CreationDate: Tue Oct 11 21:34:50 2016 -->
+<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
 "http://www.w3.org/TR/html4/loose.dtd">
 <html>
@@ -41,7 +41,7 @@
 
 
 <p style="margin-left:11%; margin-top: 1em"><b>vlmcsd.ini</b>
-&minus; vlmcsd KMS emulator configuration file</p>
+- vlmcsd KMS emulator configuration file</p>
 
 <h2>SYNOPSIS
 <a name="SYNOPSIS"></a>
@@ -267,8 +267,8 @@ randomized. The <i>argument</i> must be a number between 1
 and 32767. While any number in that range is valid, you
 should use an offcial LCID. A list of assigned LCIDs can be
 found at
-http://msdn.microsoft.com/en&minus;us/goglobal/bb964664.aspx.
-On the command line you control this setting with option
+http://msdn.microsoft.com/en-us/goglobal/bb964664.aspx. On
+the command line you control this setting with option
 <b>-C</b>.</p> </td></tr>
 </table>
 
@@ -339,6 +339,53 @@ each activation will be logged. You use <b>-v</b> and
 <b>LogVerbose</b> has an effect only if you specify a log
 file or redirect logging to <b>stdout</b>(3).</p>
 
+<p style="margin-left:11%;"><b>WhitelistingLevel</b></p>
+
+<p style="margin-left:22%;">Can be 0, 1, 2 or 3. The
+default is 0. Sets the whitelisting level to determine which
+products vlmcsd activates or refuses.</p>
+
+<p style="margin-left:29%; margin-top: 1em"><b>0</b>:
+activate all products with an unknown, retail or
+beta/preview KMS ID. <b><br>
+1</b>: activate products with a retail or beta/preview KMS
+ID but refuse to activate products with an unknown KMS ID.
+<b><br>
+2</b>: activate products with an unknown KMS ID but refuse
+products with a retail or beta/preview KMS ID. <b><br>
+3</b>: activate only products with a known volume license
+RTM KMS ID and refuse all others.</p>
+
+<table width="100%" border="0" rules="none" frame="void"
+       cellspacing="0" cellpadding="0">
+<tr valign="top" align="left">
+<td width="22%"></td>
+<td width="78%">
+
+
+<p>The SKU ID is not checked. Like a genuine KMS server
+vlmcsd activates a product that has a random or unknown SKU
+ID. If you select <b>1</b> or <b>3</b>, vlmcsd also checks
+the Application ID for correctness. If Microsoft introduces
+a new KMS ID for a new product, you cannot activate it if
+you used <b>1</b> or <b>3</b> until a new version of vlmcsd
+is available.</p></td></tr>
+</table>
+
+<p style="margin-left:11%;"><b>CheckClientTime</b></p>
+
+<p style="margin-left:22%;">Can be TRUE or FALSE. The
+default is FALSE. If you set this to TRUE <b>vlmcsd</b>(8)
+checks if the client time differs no more than four hours
+from the system time. This is useful to prevent emulator
+detection. A client that tries to detect an emulator could
+simply send two subsequent request with two time stamps that
+differ more than four hours from each other. If both
+requests succeed, the server is an emulator. If you set this
+to TRUE on a system with no reliable time source,
+activations will fail. It is ok to set the correct system
+time after you started <b>vlmcsd</b>(8).</p>
+
 <p style="margin-left:11%;"><b>ActivationInterval</b></p>
 
 <p style="margin-left:22%;">This is the same as specifying
@@ -465,8 +512,8 @@ UTF-8 is not the default encoding for most editors.</p>
 
 <p style="margin-left:11%; margin-top: 1em">If you are
 specifying an optional HWID it follows the same syntax as in
-the <b>&minus;H</b> option in <b>vlmcsd</b>(8) ecxept that
-you must not enclose a HWID in quotes even if it contains
+the <b>-H</b> option in <b>vlmcsd</b>(8) ecxept that you
+must not enclose a HWID in quotes even if it contains
 spaces.</p>
 
 <h2>FILES

man/vlmcsd.ini.5.unix.txt

@@ -208,88 +208,123 @@ KEYWORDS
               logging to stdout(3).
 
 
+       WhitelistingLevel
+              Can  be  0,  1,  2 or 3. The default is 0. Sets the whitelisting
+              level to determine which products vlmcsd activates or refuses.
+
+                   0:  activate  all  products  with  an  unknown,  retail  or
+                   beta/preview KMS ID.
+                   1:  activate  products with a retail or beta/preview KMS ID
+                   but refuse to activate products with an unknown KMS ID.
+                   2: activate products with an  unknown  KMS  ID  but  refuse
+                   products with a retail or beta/preview KMS ID.
+                   3:  activate  only products with a known volume license RTM
+                   KMS ID and refuse all others.
+
+
+              The SKU ID is not checked. Like  a  genuine  KMS  server  vlmcsd
+              activates  a product that has a random or unknown SKU ID. If you
+              select 1 or 3, vlmcsd also checks the Application  ID  for  cor‐
+              rectness.  If  Microsoft introduces a new KMS ID for a new prod‐
+              uct, you cannot activate it if you used 1 or 3 until a new  ver‐
+              sion of vlmcsd is available.
+
+
+       CheckClientTime
+              Can  be  TRUE or FALSE. The default is FALSE. If you set this to
+              TRUE vlmcsd(8) checks if the client time differs  no  more  than
+              four  hours from the system time. This is useful to prevent emu‐
+              lator detection. A client that tries to detect an emulator could
+              simply  send  two  subsequent  request with two time stamps that
+              differ more than four hours from each other.  If  both  requests
+              succeed, the server is an emulator. If you set this to TRUE on a
+              system with no reliable time source, activations will  fail.  It
+              is  ok  to  set  the  correct system time after you started vlm‐
+              csd(8).
+
+
        ActivationInterval
-              This  is the same as specifying -A on the command line. See vlm‐
+              This is the same as specifying -A on the command line. See  vlm‐
               csd(8) for details. The default is 2 hours. Example: Activation‐
               Interval = 1h
 
 
        RenewalInterval
-              This  is the same as specifying -R on the command line. See vlm‐
-              csd(8) for details. The default is 7 days.  Example:  RenewalIn‐
+              This is the same as specifying -R on the command line. See  vlm‐
+              csd(8)  for  details. The default is 7 days. Example: RenewalIn‐
               terval = 3d. Please note that the KMS client decides itself when
               to renew activation. Even though vlmcsd sends the renewal inter‐
-              val  you specify, it is no more than some kind of recommendation
-              to the client. Older KMS clients did follow  the  recommendation
+              val you specify, it is no more than some kind of  recommendation
+              to  the  client. Older KMS clients did follow the recommendation
               from a KMS server or emulator. Newer clients do not.
 
 
-       User   Run  vlmcsd  as  another, preferrably less privileged, user. The
-              argument can be a user name or a numeric user id. You must  have
-              the  required  privileges  (capabilities on Linux) to change the
-              security context of a process without providing any  credentials
-              (a  password in most cases). On most unixoid OSses 'root' is the
+       User   Run vlmcsd as another, preferrably less  privileged,  user.  The
+              argument  can be a user name or a numeric user id. You must have
+              the required privileges (capabilities on Linux)  to  change  the
+              security  context of a process without providing any credentials
+              (a password in most cases). On most unixoid OSses 'root' is  the
               only user who has these privileges in the default configuration.
-              This  setting  is not available in the native Windows version of
-              vlmcsd. See -u in vlmcsd(8). This setting cannot be  changed  on
+              This setting is not available in the native Windows  version  of
+              vlmcsd.  See  -u in vlmcsd(8). This setting cannot be changed on
               the fly by sending SIGHUP to vlmcsd.
 
 
-       Group  Run  vlmcsd  as another, preferrably less privileged, group. The
-              argument can be a group name or a numeric  group  id.  You  must
-              have  the  required privileges (capabilities on Linux) to change
-              the security context of a process without providing any  creden‐
-              tials  (a  password in most cases). On most unixoid OSses 'root'
+       Group  Run vlmcsd as another, preferrably less privileged,  group.  The
+              argument  can  be  a  group name or a numeric group id. You must
+              have the required privileges (capabilities on Linux)  to  change
+              the  security context of a process without providing any creden‐
+              tials (a password in most cases). On most unixoid  OSses  'root'
               is the only user who has these privileges in the default config‐
-              uration.  This  setting  is  not available in the native Windows
-              version of vlmcsd. See -g in vlmcsd(8). This setting  cannot  be
+              uration. This setting is not available  in  the  native  Windows
+              version  of  vlmcsd. See -g in vlmcsd(8). This setting cannot be
               changed on the fly by sending SIGHUP to vlmcsd.
 
 
        Windows
-              The  argument  has the form ePID [ / HwId ]. Always use ePID and
-              HwId for Windows activations. If  specified,  RandomizationLevel
+              The argument has the form ePID [ / HwId ]. Always use  ePID  and
+              HwId  for  Windows activations. If specified, RandomizationLevel
               for Windows activitations will be ignored.
 
 
        Office2010
-              The  argument  has the form ePID [ / HwId ]. Always use ePID and
-              HwId for Office 2010 activations. If  specified,  Randomization‐
+              The argument has the form ePID [ / HwId ]. Always use  ePID  and
+              HwId  for  Office 2010 activations. If specified, Randomization‐
               Level for Office 2010 activitations will be ignored.
 
 
        Office2013
-              The  argument  has the form ePID [ / HwId ]. Always use ePID and
-              HwId for Office 2013 activations. If  specified,  Randomization‐
+              The argument has the form ePID [ / HwId ]. Always use  ePID  and
+              HwId  for  Office 2013 activations. If specified, Randomization‐
               Level for Office 2013 activitations will be ignored.
 
 
        Office2016
-              The  argument  has the form ePID [ / HwId ]. Always use ePID and
-              HwId for Office 2016 activations. If  specified,  Randomization‐
+              The argument has the form ePID [ / HwId ]. Always use  ePID  and
+              HwId  for  Office 2016 activations. If specified, Randomization‐
               Level for Office 2016 activitations will be ignored.
 
 
 VALID EPIDS
-       The  ePID is currently a comment only. You can specify any string up to
-       63 bytes. In Windows 7 Microsoft has blacklisted few (  <  10  )  ePIDs
-       that  were  used  in KMSv5 versions of the "Ratiborus Virtual Machine".
-       Microsoft has given up on blacklisting when KMS emulators  appeared  in
+       The ePID is currently a comment only. You can specify any string up  to
+       63  bytes.  In  Windows  7 Microsoft has blacklisted few ( < 10 ) ePIDs
+       that were used in KMSv5 versions of the  "Ratiborus  Virtual  Machine".
+       Microsoft  has  given up on blacklisting when KMS emulators appeared in
        the wild.
 
        Even if you can use "Activated by cool hacker guys" as an ePID, you may
        wish to use ePIDs that cannot be detected as non-MS ePIDs. If you don't
-       know  how  these  "valid"  ePIDs look like exactly, do not use GUIDS in
-       vlmcsd.ini. vlmcsd  provides  internal  mechanisms  to  generate  valid
+       know how these "valid" ePIDs look like exactly, do  not  use  GUIDS  in
+       vlmcsd.ini.  vlmcsd  provides  internal  mechanisms  to  generate valid
        ePIDs.
 
        If you use non-ASCII characters in your ePID (you shouldn't do anyway),
-       these must be in UTF-8 format. This is especially  important  when  you
+       these  must  be  in UTF-8 format. This is especially important when you
        run vlmcsd on Windows or cygwin because UTF-8 is not the default encod‐
        ing for most editors.
 
        If you are specifying an optional HWID it follows the same syntax as in
-       the  -H  option in vlmcsd(8) ecxept that you must not enclose a HWID in
+       the -H option in vlmcsd(8) ecxept that you must not enclose a  HWID  in
        quotes even if it contains spaces.
 
 
@@ -303,7 +338,7 @@ AUTHOR
 
 
 CREDITS
-       Thanks  to  CODYQX4,  deagles,  eIcn, mikmik38, nosferati87, qad, Rati‐
+       Thanks to CODYQX4, deagles, eIcn,  mikmik38,  nosferati87,  qad,  Rati‐
        borus, ...
 
 
@@ -312,4 +347,4 @@ SEE ALSO
 
 
 
-Hotbird64                       September 2016                   VLMCSD.INI(5)
+Hotbird64                        October 2016                    VLMCSD.INI(5)

man/vlmcsdmulti.1.html

@@ -1,5 +1,5 @@
 <!-- Creator     : groff version 1.22.3 -->
-<!-- CreationDate: Tue Oct 11 21:34:50 2016 -->
+<!-- CreationDate: Fri Oct 21 03:17:10 2016 -->
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
 "http://www.w3.org/TR/html4/loose.dtd">
 <html>
@@ -36,8 +36,8 @@
 </h2>
 
 
-<p style="margin-left:11%; margin-top: 1em">vlmcsdmulti
-&minus; a multi-call binary containing <b>vlmcs</b>(1) and
+<p style="margin-left:11%; margin-top: 1em">vlmcsdmulti - a
+multi-call binary containing <b>vlmcs</b>(1) and
 <b>vlmcsd</b>(8)</p>
 
 <h2>SYNOPSIS

src/GNUmakefile

@@ -62,7 +62,7 @@ DNS_PARSER ?= OS
 
 # You should supply your own version string here
 
-VLMCSD_VERSION ?= $(shell test -d .svn && echo svn`svnversion`)
+VLMCSD_VERSION ?= $(shell test -d ../.svn && echo svn`svnversion`)
 
 FEATURES ?= full
 VERBOSE ?= NO
@@ -251,14 +251,14 @@ else
   STRIPFLAGS += -s
 endif
 
-LIBRARY_CFLAGS = -DSIMPLE_SOCKETS -DNO_TIMEOUT -DNO_SIGHUP -DNO_CL_PIDS -DNO_EXTENDED_PRODUCT_LIST -DNO_BASIC_PRODUCT_LIST -DNO_LOG -DNO_RANDOM_EPID -DNO_INI_FILE -DNO_HELP -DNO_CUSTOM_INTERVALS -DNO_PID_FILE -DNO_USER_SWITCH -DNO_VERBOSE_LOG -DNO_LIMIT -DNO_VERSION_INFORMATION -DNO_PRIVATE_IP_DETECT
+LIBRARY_CFLAGS = -DSIMPLE_SOCKETS -DNO_TIMEOUT -DNO_SIGHUP -DNO_CL_PIDS -DNO_EXTENDED_PRODUCT_LIST -DNO_BASIC_PRODUCT_LIST -DNO_LOG -DNO_RANDOM_EPID -DNO_INI_FILE -DNO_HELP -DNO_CUSTOM_INTERVALS -DNO_PID_FILE -DNO_USER_SWITCH -DNO_VERBOSE_LOG -DNO_LIMIT -DNO_VERSION_INFORMATION -DNO_PRIVATE_IP_DETECT -UNO_SOCKETS -USIMPLE_RPC
 
 ifeq ($(FEATURES), embedded)
   BASECFLAGS += -DNO_HELP -DNO_USER_SWITCH -DNO_BASIC_PRODUCT_LIST -DNO_CUSTOM_INTERVALS -DNO_PID_FILE -DNO_VERBOSE_LOG -DNO_VERSION_INFORMATION
 else ifeq ($(FEATURES), autostart)
   BASECFLAGS += -DNO_HELP -DNO_VERSION_INFORMATION
 else ifeq ($(FEATURES), minimum)
-  BASECFLAGS += -DSIMPLE_SOCKETS -DNO_TIMEOUT -DNO_SIGHUP -DNO_CL_PIDS -DNO_EXTENDED_PRODUCT_LIST -DNO_BASIC_PRODUCT_LIST -DNO_LOG -DNO_RANDOM_EPID -DNO_INI_FILE -DNO_HELP -DNO_CUSTOM_INTERVALS -DNO_PID_FILE -DNO_USER_SWITCH -DNO_VERBOSE_LOG -DNO_LIMIT -DNO_VERSION_INFORMATION -DNO_PRIVATE_IP_DETECT -DSMALL_AES
+  BASECFLAGS += -DSIMPLE_RPC -DSIMPLE_SOCKETS -DNO_TIMEOUT -DNO_SIGHUP -DNO_CL_PIDS -DNO_EXTENDED_PRODUCT_LIST -DNO_BASIC_PRODUCT_LIST -DNO_LOG -DNO_RANDOM_EPID -DNO_INI_FILE -DNO_HELP -DNO_CUSTOM_INTERVALS -DNO_PID_FILE -DNO_USER_SWITCH -DNO_VERBOSE_LOG -DNO_LIMIT -DNO_VERSION_INFORMATION -DNO_PRIVATE_IP_DETECT -DSMALL_AES
 else ifeq ($(FEATURES), most)
   BASECFLAGS += -DNO_SIGHUP -DNO_PID_FILE -DNO_LIMIT
 else ifeq ($(FEATURES), inetd)