Contents
console
pyarmor reg
First of all
- An
activation file
ofPyarmor License
likepyarmor-regcode-xxxx.txt
, refer to../licenses
to purchase right one - Pyarmor 8.2+
- Internet connection
- Product name bind to this license, for non-commercial use, product name is
non-profits
Basic use steps:
- Using
activation file
to initial registration, set product name bind to this license - Once initial registration completed, a
registration file
is generated - Using
registration file
to register Pyarmor in other devices
Using -p
to specify product name for this license, for non-commercial use, set product name to non-profits
.
Assume this license is used to protect your product XXX
, initial registration by this command:
$ pyarmor reg -p "XXX" pyarmor-regcode-xxxx.txt
Pyarmor will show registration information and ask for your confirmation. If everything is fine, type yes
and Enter
to continue. Any other input aborts registration.
If initial registration is successful, it prints final license information in the console. And a registration file
like pyarmor-regfile-xxxx.zip
is generated in the current path at the same time. This file is used for subsequent registration in other machines.
Once initial registration completed, activation file pyarmor-regcode-xxxx.txt
is invalid, do not use it again.
Once initial registration completed, product name can't be changed.
Please backup registration file pyarmor-regfile-xxxx.zip
carefully. If lost, Pyarmor is not responsible for keeping this license and no lost-found service.
When product is in developing, and product name is not decided. Set product name to TBD
on initial registration. For example:
$ pyarmor reg -p "TBD" pyarmor-regcode-xxxx.txt
In 6 months real product name must be set by this command:
$ pyarmor reg -p "XXX" pyarmor-regcode-xxxx.txt
If it's not changed after 6 months, the product name will be set to non-profits
automatically and can't be changed again.
Copy registration file
pyarmor-regfile-xxxx.zip
to other machines, run the following command:
$ pyarmor reg pyarmor-regfile-xxxx.zip
Check the registration information:
$ pyarmor -v
After successful registration, all obfuscations will automatically apply this license, and each obfuscation requires online license verification.
It's no problem to run Pyarmor in Docker or CI pipeline to obfuscate user's application. Register pyarmor with pyarmor-regfile-xxxx.zip
same as above. But It's not allowed to distribute pyarmor self and any Pyarmor License to customer
Don't run too many build dockers, maximum is 100.
8.2
Each Pyarmor Group
could have 100 offline devices, each device has its own number, from 1 to 100.
Basic use steps:
- Using activation file
pyarmor-regcode-xxxx.txt
to initial registration, set product name bind to this license, and generateregistration file
1 - Generating group device file separately on each offline device
- Using
registration file
and group device file to generate device registration file. - Using device registration file to register Pyarmor on offline device2
After purchasing Pyarmor Group
, an activation file pyarmor-regcode-xxxx.txt
is sent to registration email.
Initial registration need internet connection and Pyarmor 8.2+. Suppose product name is XXX
, then run this command:
$ pyarmor reg -p XXX pyarmor-regcode-xxxx.txt
After initial registration completed, a registration file
pyarmor-regfile-xxxx.zip
will be generated.
On each offline device, install Pyarmor 8.2+, and generate group device file. For example, on device no. 1, run this command:
$ pyarmor reg -g 1
It will generate group device file pyarmor-group-device.1
.
Generating offline device regfile need internet connection, Pyarmor 8.2+, group device file pyarmor-group-device.1
and group license registration file
pyarmor-regfile-xxxx.zip
.
Copying group device file pyarmor-group-device.1
to initial registration device or any computer which has internet connection and registration file, this file must be saved in the path .pyarmor/group/
, then run the following command to generate device regfile pyarmor-device-regfile-xxxx.1.zip
:
$ mkdir -p .pyarmor/group
$ cp pyarmor-group-device.1 .pyarmor/group/
$ pyarmor reg -g 1 /path/to/pyarmor-regfile-xxxx.zip
Once device regfile is generated, copy it to the corresponding device, run this command to register Pyarmor:
$ pyarmor reg pyarmor-device-regfile-xxxx.1.zip
Check registration information:
$ pyarmor -v
After successful registration, all obfuscations will automatically apply this group license, and each obfuscation need not online license verification.
Refer to upgrade old license <upgrading old license>