modified: nfig1.py

[GalaxyCodeBases.git] / etc / Windows / vlmcsd / man / vlmcsd.ini.5.dos.txt

VLMCSD.INI(5)                KMS Activation Manual               VLMCSD.INI(5)\r
\r
\r
\r
NAME\r
       vlmcsd.ini - vlmcsd KMS emulator configuration file\r
\r
\r
SYNOPSIS\r
       vlmcsd.ini\r
\r
\r
DESCRIPTION\r
       vlmcsd.ini  (or  simply  called the "ini file") is a configuration file\r
       for vlmcsd(8). By default vlmcsd does not use a configuration file.  It\r
       is completely optional and for advanced users only. You must use the -i\r
       option on the vlmcsd command line to use  an  ini  file.  There  is  no\r
       default name or default location for the ini file.\r
\r
       Everything,  that can be configured in the ini file, may also be speci‐\r
       fied on the command line. Any configuration  option  specified  on  the\r
       command line takes precedence over the respective configuration line in\r
       the ini file.\r
\r
       Benefits of a configuration file\r
\r
       While you can use the configuration file to simply modify  the  default\r
       behavior  of vlmcsd, it can also be used to change the configuration of\r
       vlmcsd after you sent a HUP signal(7). Whenever you  send  SIGHUP,  the\r
       configuration  file  will  be  re-read. Any changes you made to the ini\r
       file will be reflected after vlmcsd received the hangup signal.\r
\r
       Differences between command line and configuration file\r
\r
       If you specify an illegal option or  option  argument  on  the  command\r
       line,  vlmcsd displays help and exits. If you specify an incorrect key‐\r
       word or argument in the ini file, vlmcsd displays a warning  with  some\r
       information,  ignores the respective line and continues. This is inten‐\r
       tional and prevents vlmcsd from aborting after a SIGHUP if the configu‐\r
       ration was modified incorrectly.\r
\r
\r
SYNTAX\r
       vlmcsd.ini  is  a  UTF-8  encoded text file with each line being in the\r
       format keyword = argument. The keyword is not case-sensitive. The argu‐\r
       ment  is  treated  literally.  It  is  neither  required nor allowed to\r
       enclose the argument in any form of quote characters except when  quote\r
       characters  are  part of the argument itself. Whitespace characters are\r
       ignored only\r
\r
       - at the beginning of a line\r
       - between the keyword and '='\r
       - between '=' and the argument\r
\r
       Lines, that start with '#' or ';' are treated as comments. Empty  lines\r
       are  ignored  as well. If a keyword is repeated in another line, vlmcsd\r
       will use the argument of the last occurence of the keyword.  An  excep‐\r
       tion  to  this  is  the  Listen keyword which can be specified multiple\r
       times and causes vlmcsd to listen on more than one  IP  address  and/or\r
       port.\r
\r
       Some  arguments  are  binary  arguments  that need to be either TRUE or\r
       FALSE. You can use "Yes", "On" or "1" as an alias for  TRUE  and  "No",\r
       "Off"  or "0" as an alias for FALSE. Binary arguments are case-insensi‐\r
       tive.\r
\r
\r
KEYWORDS\r
       The following keywords are defined (not all keywords may  be  available\r
       depending  on  the operating system and the options used when vlmcsd(8)\r
       was compiled):\r
\r
\r
       Listen This defines on what combinations of IP addresses and ports vlm‐\r
              csd  should  listen. Listen can be specified more than once. The\r
              argument has the form ipaddress[:port]. If you  omit  the  port,\r
              the  default  port  of  1688  is used. If the ipaddress contains\r
              colons and a port is used, you must  enclose  the  ipaddress  in\r
              brackets. The default is to listen to 0.0.0.0:1688 and [::]:1688\r
              which means listen to all IPv4 and all IPv6 addresses.  See  the\r
              -L  option  in  vlmcsd(8) for more info about the syntax. If you\r
              use -L or -P on the command line, all Listen keywords in the ini\r
              file  will be ignored. The Listen keyword cannot be used if vlm‐\r
              csd has been compiled to use Microsoft RPC (Windows  and  Cygwin\r
              only) or simple sockets.\r
\r
              Examples:\r
\r
              Listen = 192.168.1.123:1688\r
              Listen = 0.0.0.0:1234\r
              Listen = [fe80::1721:12ff:fe81:d36b%eth0]:1688\r
\r
\r
       Port   Can only be used if vlmcsd has been compiled to use simple sock‐\r
              ets or on Windows and Cygwin if vlmcsd(8) has been  compiled  to\r
              use Microsoft RPC. Otherwise you must use Listen instead. Causes\r
              vlmcsd to listen on that port instead of 1688.\r
\r
\r
       FreeBind\r
              Can be TRUE or FALSE. If TRUE, you can use  the  Listen  keyword\r
              with IP addresses that are currently not defined on your system.\r
              vlmcsd(8) will start listening on these IP addresses as soon  as\r
              they  become  available.  This  keyword  is only available under\r
              Linux and FreeBSD because no other OS  currently  supports  that\r
              feature.  FreeBSD  supports  this only for IPv4 and requires the\r
              PRIV_NETINET_BINDANY privilege which  is  normally  assigned  to\r
              proccesses of the root user.\r
\r
\r
       PublicIPProtectionLevel\r
              Set  the level of protection against KMS activations from public\r
              IP addresses.\r
\r
              0 = No protection (default)\r
              1 = Listen on private IP addresses only (plus those specified by\r
              one or more Listen statements)\r
              2 = Disconnect clients with public IP addresses without activat‐\r
              ing\r
              3 = Combines 1 and 2\r
\r
              For details on public IP protection levels see vlmcsd(8) command\r
              line option -o.\r
\r
\r
       UseNDR64\r
              Can  be  TRUE  or  FALSE.  Specifies whether you want to use the\r
              NDR64 transfer syntax. See options -n0 and -n1 in vlmcsd(8). The\r
              default is TRUE.\r
\r
\r
       UseBTFN\r
              Can  be  TRUE  or  FALSE. Specifies whether you want to use bind\r
              time feature negotiation in RPC. See options -b0 and -b1 in vlm‐\r
              csd(8). The default is TRUE.\r
\r
\r
       RandomizationLevel\r
              The  argument must 0, 1 or 2. This specifies the ePID randomiza‐\r
              tion level. See options -r0,  -r1  and  -r2  in  vlmcsd(8).  The\r
              default  randomization  level is 1. A RandomizationLevel of 2 is\r
              not recommended and should be treated as a debugging level.\r
\r
\r
       LCID   Use a specific culture id (LCID) even if the ePID is randomized.\r
              The  argument  must  be  a number between 1 and 32767. While any\r
              number in that range is valid, you should use an offcial LCID. A\r
              list  of  assigned  LCIDs  can  be  found  at http://msdn.micro‐\r
              soft.com/en-us/goglobal/bb964664.aspx. On the command  line  you\r
              control this setting with option -C.\r
\r
\r
       MaxWorkers\r
              The argument specifies the maximum number of worker processes or\r
              threads that will be used to serve activation  requests  concur‐\r
              rently.  This  is the same as specifying -m on the command line.\r
              Minimum is 1. The maximum is platform specific and is  at  least\r
              32767  but  is likely to be greater on most systems. The default\r
              is no limit.\r
\r
\r
       ConnectionTimeout\r
              Used to control when the vlmcsd  disconnects  idle  TPC  connec‐\r
              tions. The default is 30 seconds. This is the same setting as -t\r
              on the command line.\r
\r
\r
       DisconnectClientsImmediately\r
              Set this to TRUE to disconnect a client after it got an  activa‐\r
              tion  response  regardless whether a timeout has occured or not.\r
              The default is FALSE.  Setting  this  to  TRUE  is  non-standard\r
              behavior.  Use only if you are experiencing DoS or DDoS attacks.\r
              On the command line you control this behavior  with  options  -d\r
              and -k.\r
\r
\r
       PidFile\r
              Write  a  pid  file.  The argument is the full pathname of a pid\r
              file. The pid  file  contains  is  single  line  containing  the\r
              process  id  of  the  vlmcsd  process.  It  can  be used to stop\r
              (SIGTERM) or restart (SIGHUP)  vlmcsd.  This  directive  can  be\r
              overriden using -p on the command line.\r
\r
\r
       LogFile\r
              Write  a  log  file.  The argument is the full pathname of a log\r
              file. On a unixoid OS and with Cygwin you can  use  the  special\r
              filename  'syslog'  to  log  to the syslog facility. This is the\r
              same as specifying -l on the command line.\r
\r
\r
       LogDateAndTime\r
              Can be TRUE or FALSE. The default is TRUE. If set to FALSE, log‐\r
              ging  output  does  not include date and time. This is useful if\r
              you log to stdout(3) which  is  redirected  to  another  logging\r
              mechanism that already includes date and time in its output, for\r
              instance systemd-journald(8). If you log to syslog(3),  LogDate‐\r
              AndTime  is  ignored and date and time will never be included in\r
              the output sent to syslog(3). Using the command line you control\r
              this setting with options -T0 and -T1.\r
\r
\r
       LogVerbose\r
              Set  this  to either TRUE or FALSE. The default is FALSE. If set\r
              to TRUE, more details of each activation will be logged. You use\r
              -v  and  -q in the command line to control this setting. LogVer‐\r
              bose has an effect only if you specify a log  file  or  redirect\r
              logging to stdout(3).\r
\r
\r
       WhitelistingLevel\r
              Can  be  0,  1,  2 or 3. The default is 0. Sets the whitelisting\r
              level to determine which products vlmcsd activates or refuses.\r
\r
                   0:  activate  all  products  with  an  unknown,  retail  or\r
                   beta/preview KMS ID.\r
                   1:  activate  products with a retail or beta/preview KMS ID\r
                   but refuse to activate products with an unknown KMS ID.\r
                   2: activate products with an  unknown  KMS  ID  but  refuse\r
                   products with a retail or beta/preview KMS ID.\r
                   3:  activate  only products with a known volume license RTM\r
                   KMS ID and refuse all others.\r
\r
\r
              The SKU ID is not checked. Like  a  genuine  KMS  server  vlmcsd\r
              activates  a product that has a random or unknown SKU ID. If you\r
              select 1 or 3, vlmcsd also checks the Application  ID  for  cor‐\r
              rectness.  If  Microsoft introduces a new KMS ID for a new prod‐\r
              uct, you cannot activate it if you used 1 or 3 until a new  ver‐\r
              sion of vlmcsd is available.\r
\r
\r
       CheckClientTime\r
              Can  be  TRUE or FALSE. The default is FALSE. If you set this to\r
              TRUE vlmcsd(8) checks if the client time differs  no  more  than\r
              four  hours from the system time. This is useful to prevent emu‐\r
              lator detection. A client that tries to detect an emulator could\r
              simply  send  two  subsequent  request with two time stamps that\r
              differ more than four hours from each other.  If  both  requests\r
              succeed, the server is an emulator. If you set this to TRUE on a\r
              system with no reliable time source, activations will  fail.  It\r
              is  ok  to  set  the  correct system time after you started vlm‐\r
              csd(8).\r
\r
\r
       MaintainClients\r
              Can be TRUE or FALSE (the default). Disables (FALSE) or  enables\r
              (TRUE) maintaining a list of client machine IDs (CMIDs). TRUE is\r
              useful to prevent emulator detection. By maintaing a CMID  list,\r
              vlmcsd(8)  reports current active clients exactly like a genuine\r
              KMS emulator. This includes bug compatibility to the extent that\r
              you  can  permanently  kill a genuine KMS emulator by sending an\r
              "overcharge request" with a required client count of 376 or more\r
              and  then  request  activation for 671 clients. vlmcsd(8) can be\r
              reset from this condition by restarting it. If  FALSE  is  used,\r
              vlmcsd(8) reports current active clients as good as possible. If\r
              no client sends an "overcharge request", it is not  possible  to\r
              detect  vlmcsd(8)  as  an emulator with MaintainClients = FALSE.\r
              Maintaining clients requires the allocation of a buffer that  is\r
              about  50  kB in size. On hardware with few memory resources use\r
              it only if you really need it.\r
\r
              If you start vlmcsd(8) from an internet superserver,  this  set‐\r
              ting  cannot  be  used. Since vlmcsd(8) exits after each activa‐\r
              tion, it cannot maintain any state in memory.\r
\r
\r
       StartEmpty\r
              This setting is ignored if you do  not  also  specify  Maintain‐\r
              Clients  =  TRUE.  If you specify FALSE (the default), vlmcsd(8)\r
              starts up as a fully  "charged"  KMS  server.  Clients  activate\r
              immediately.  StartEmpty = TRUE lets you start up vlmcsd(8) with\r
              an empty CMID list. Activation will start when the required min‐\r
              imum  clients (25 for Windows Client OSses, 5 for Windows Server\r
              OSses and Office) have registered with the KMS server.  As  long\r
              as the minimum client count has not been reached, clients end up\r
              in HRESULT 0xC004F038 "The count reported by your Key Management\r
              Service (KMS) is insufficient. Please contact your system admin‐\r
              istrator". You may use vlmcs(1) or another KMS  client  emulator\r
              to  "charge"  vlmcsd(8). Setting this parameter to TRUE does not\r
              improve emulator detection prevention. It's primary  purpose  is\r
              to  help  developers  of  KMS  clients  to test "charging" a KMS\r
              server.\r
\r
\r
       ActivationInterval\r
              This is the same as specifying -A on the command line. See  vlm‐\r
              csd(8) for details. The default is 2 hours. Example: Activation‐\r
              Interval = 1h\r
\r
\r
       RenewalInterval\r
              This is the same as specifying -R on the command line. See  vlm‐\r
              csd(8)  for  details. The default is 7 days. Example: RenewalIn‐\r
              terval = 3d. Please note that the KMS client decides itself when\r
              to renew activation. Even though vlmcsd sends the renewal inter‐\r
              val you specify, it is no more than some kind of  recommendation\r
              to  the  client. Older KMS clients did follow the recommendation\r
              from a KMS server or emulator. Newer clients do not.\r
\r
\r
       User   Run vlmcsd as another, preferrably less  privileged,  user.  The\r
              argument  can be a user name or a numeric user id. You must have\r
              the required privileges (capabilities on Linux)  to  change  the\r
              security  context of a process without providing any credentials\r
              (a password in most cases). On most unixoid OSses 'root' is  the\r
              only user who has these privileges in the default configuration.\r
              This setting is not available in the native Windows  version  of\r
              vlmcsd.  See  -u in vlmcsd(8). This setting cannot be changed on\r
              the fly by sending SIGHUP to vlmcsd.\r
\r
\r
       Group  Run vlmcsd as another, preferrably less privileged,  group.  The\r
              argument  can  be  a  group name or a numeric group id. You must\r
              have the required privileges (capabilities on Linux)  to  change\r
              the  security context of a process without providing any creden‐\r
              tials (a password in most cases). On most unixoid  OSses  'root'\r
              is the only user who has these privileges in the default config‐\r
              uration. This setting is not available  in  the  native  Windows\r
              version  of  vlmcsd. See -g in vlmcsd(8). This setting cannot be\r
              changed on the fly by sending SIGHUP to vlmcsd.\r
\r
\r
       Windows\r
              The argument has the form ePID [ / HwId ]. Always use  ePID  and\r
              HwId  for  Windows activations. If specified, RandomizationLevel\r
              for Windows activitations will be ignored.\r
\r
\r
       Office2010\r
              The argument has the form ePID [ / HwId ]. Always use  ePID  and\r
              HwId  for  Office 2010 activations. If specified, Randomization‐\r
              Level for Office 2010 activitations will be ignored.\r
\r
\r
       Office2013\r
              The argument has the form ePID [ / HwId ]. Always use  ePID  and\r
              HwId  for  Office 2013 activations. If specified, Randomization‐\r
              Level for Office 2013 activitations will be ignored.\r
\r
\r
       Office2016\r
              The argument has the form ePID [ / HwId ]. Always use  ePID  and\r
              HwId  for  Office 2016 activations. If specified, Randomization‐\r
              Level for Office 2016 activitations will be ignored.\r
\r
\r
VALID EPIDS\r
       The ePID is currently a comment only. You can specify any string up  to\r
       63  bytes.  In  Windows  7 Microsoft has blacklisted few ( < 10 ) ePIDs\r
       that were used in KMSv5 versions of the  "Ratiborus  Virtual  Machine".\r
       Microsoft  has  given up on blacklisting when KMS emulators appeared in\r
       the wild.\r
\r
       Even if you can use "Activated by cool hacker guys" as an ePID, you may\r
       wish to use ePIDs that cannot be detected as non-MS ePIDs. If you don't\r
       know how these "valid" ePIDs look like exactly, do  not  use  GUIDS  in\r
       vlmcsd.ini.  vlmcsd  provides  internal  mechanisms  to  generate valid\r
       ePIDs.\r
\r
       If you use non-ASCII characters in your ePID (you shouldn't do anyway),\r
       these  must  be  in UTF-8 format. This is especially important when you\r
       run vlmcsd on Windows or cygwin because UTF-8 is not the default encod‐\r
       ing for most editors.\r
\r
       If you are specifying an optional HWID it follows the same syntax as in\r
       the -H option in vlmcsd(8) ecxept that you must not enclose a  HWID  in\r
       quotes even if it contains spaces.\r
\r
\r
FILES\r
       vlmcsd.ini(5)\r
\r
\r
AUTHOR\r
       vlmcsd(8) was written by crony12, Hotbird64 and vityan666. With contri‐\r
       butions from DougQaid.\r
\r
\r
CREDITS\r
       Thanks to CODYQX4, deagles, eIcn,  mikmik38,  nosferati87,  qad,  Rati‐\r
       borus, ...\r
\r
\r
SEE ALSO\r
       vlmcsd(8), vlmcsd(7), vlmcs(1), vlmcsdmulti(1)\r
\r
\r
\r
Hotbird64                        October 2016                    VLMCSD.INI(5)\r