Usage

Top  Previous  Next

 

licgen [options] output.lic

 

--expire <dd/mm/yyyy>                Set license expiration date

--expire <00d[00h[00m[00s]]]>        Set license expiration time from now

--domain <domain>                Bind license to domain name

--ip <x.x.x.x[/y.y.y.y]>                Bind license to ip/mask

--mac <x:x:x:x:x:x>                Bind license to mac address

--machine-id <machine id>        Bind license to a machine id

--projid <value>                        Set project id (required, the same as for encoding)

--projkey <value>                Set project key (required, the same as for encoding)

--const name=value                Set custom defined constant

--time-server <server,server,...>        Set time server (for expiration date check)

--text "text"|@file                Add plain text into the license file

 

-l        Display RubyEncoder license information for the tool itself

-w        Wait for key press before exit

-v        Display version number

-h        Display options help

 

output.lic - This is the name of the license file to generate. It should be the same that you used in --external option during the encode.

 

It is possible to run the licgen tool with only a license file name but without any other locking options specified. It will generate the license required to run your scripts encoded with --external option but no locking will be applied to the protected scripts. To enable locking with the external license file please read  about script locking options. All locking options work the same as similar options of the rubyencoder executable.

 

You may use a -- (double dash) instead of the output file name in order to send licgen's output to console instead of a file which may be useful for automating license generation when running licgen on the server side.

 

 

Locking options

 

Most of the options work exactly the same as options of the encoder. Please refer to the Script locking options section for further details. Note, some of the options are available only for the encoder and not the license generator, e.g. --ip-encrypt, --domain-encrypt, --machine-encrypt, --remote-verification-url and some others.

 

 

Custom constants

 

You may add custom constants to license files exactly the same as you do it with the encoder. Please refer to the Custom predefined constants section for further details.

 

 

Options unique to the license generator

 

--text "text"

 

This option lets you add a custom text that will be embedded as-is into the license file and therefore that text is readable. The text is protected with a checksum against modification. You may include any text such as user information, license description etc.

 

All user {constants} that are defined with the --const option above will be replaced in the text. Also some standard RubyEncoder constants may be used:

 

       {RG_DATE} - current date i.e. date of encoding

       {RG_LICENSEE} - RubyEncoder license owner from the RubyEncoder license file (i.e.your name, not your customer's name)
       {RG_EXPIRY_DATE} - your custom license expiry date. Changing of this text in the license file does not make sense and is NOT opening a back        door, if you use the expiry date in your custom licenses. The expiry date is stored encrypted as well as other options within the license file. The        readable text is only for information and you may put a name of your product, name of your customer and the expiry date.

 

Constant names are case sensitive. It works in the same way also for the custom header in protected scripts. See details

 

The text contents may be loaded from a file: --text @textfile. All the constants replacements will be done in that case too.