Skip to main content

A python package could import/run encrypted python scripts.

Project description

Pyarmor, Guard your python scripts

Do you worry about how to protect your python scripts? Now, it's easy
with the coming of Pyarmor.

What's Pyarmor

A python package could import/run encrypted python scripts.

Who Use Pyarmor

A python developer wants to release his project, but do not want to
publish the literal scripts. What should he do?

* Use pyarmor to encrypt the python scripts
* Distribute encrypted python scripts to the customer

That's all.

Supported Python Versions

Pyarmor need python 2.6 or later, but it supports to run/import the
encrypted scripts from Python 2.3 to the latest Python by Cross
Publish (See below).

Supported platforms

Windows, Linux, including Embeded Linux are supported, The following
operation systems have been tested:

* Windows XP, Windows7 both x86 and amd64
* Ubuntu 13.04 both i686, x86_64 and armv7


Project Capsule

A zip file includes all the auxiliary files which used to import the
encrypted scripts. It's generated by Pyarmor.


* Install corresponding Python

* Run pip to install pyarmor package from

$ pip install pyarmor

* Or download the package from

* Extract the downloaded package to any path, for example,
c:/pyarmor or /opt/pyarmor

Basic Usage

The normal scenario for a developer to use pyarmor is

* Generate project capsule for each project
* Encrypt python scripts with project capsule


* Distribute the encrypted scripts to target machine

Next it's an example to show you how to use pyarmor to encrypt scripts
and how to distribute encrypted scripts.

Encrypt Script

Assume you have 2 scripts:,

* Generate project capsule

`For example,`::

$ python capsule

It will make a file "" in the current directory.

* Encrypt python scripts

`For example,`::

$ python encrypt \

After above command finished, you will find the following files in
the path "dist"

* moda.pyx
* modb.pyx

* pytransform.pyd (for windows) or (for linux)
* cygtfm-0.dll / libtfm-0.dll (only for windows)
* cygtomcrypt-0.dll / libtomcrypt-0.dll (only for windows)
* pyshield.key
* pyshield.lic
* product.key
* license.lic

The first 2 files are encrypted scripts, the others are
auxiliary. All of these files is required when distribute encrypted

`About more usage of pyarmor`::

C:/Python32/python pyarmor --help

C:/Python32/python pyarmor encrypt --help

Distribute Script

Before you distribute encrypted scripts above, you need change a
little in your main script -- add a line 'import pyimcore' before
import those encrypted module. Assume your startup script is,
what you will do is add a line in the file header somewhere.

`For example,`::

import pyimore

The main function of pyimcore is to install an import hook, so that
the encrypted module will be imported correctly. For you, everything
is transparent, all of the source code need to be changed nothing
else !

Now copy the following files to your customer:

* moda.pyx
* modb.pyx

* pytransform.pyd (for windows) or (for linux)
* cygtfm-0.dll / libtfm-0.dll (only for windows)
* cygtomcrypt-0.dll / libtomcrypt-0.dll (only for windows)
* pyshield.key
* pyshield.lic
* product.key
* license.lic

And run it as if there are no any encrypted scripts.

Generate Special "license.lic"

By default, the distribute path will include a file "license.lic",
it's required to run/import encrypted scripts. You can generate other
license file by command "license" for special users.

`Generate license.lic with registration code "MYPROJECT-001"`::

$ python license MYPROJECT-001

This command will generate a new "license.lic" with registration code
"MYPROJECT-001", replace the old with this one in "dist" path.

Advanced Usage

Run Encrypted Script

Someone maybe say I want to encrypt my startup script either, then how
to run it.

`Encrypt the script at first,`::

$ python encrypt \

`Run python with -c, for example,`::

python -c "import pyimcore
import pytransform

`Or create a startup script like this,`::

import pyimcore
import pytransform

Then run as normal python script.

You can read the source file to know the basic usage of
pytransform extension.

Cross Publish

If target machine is different from development machine, you need use
option '--with-extension' to publish encrypted scripts. A common case
is to distribute python scripts to embedded linux system. The only
difference is to replace python extension "pytransform" with the
corresponding platform.

* In the sub-directory "extensions" of pyarmor, there are many files
looks like:


X.Y is python major and minor version, ARCH may be x86, x86_64, arm etc.

`Encrypt scripts with option --with-extension`::

$ python encrypt \
--with-extension=extensions/ \

`Another example, encrypted scripts for Python2.3`::

$ python3 encrypt \
--with-extension=extensions/pytransform-1.7.2.win32-x86-py2.3.pyd \

Generate "license.lic" of Special Machine

Sometimes you want to run/import encrypted scripts in special
machine. You can generate a "license.lic" bind to serial number of
hard disk.

`Generate license.lic with serial number of hard disk "PBN2081SF3NJ5T"`::

$ python license --bind PBN2081SF3NJ5T

This command will generate a new "license.lic" bind to harddisk which
serial number is "PBN2081SF3NJ5T", replace the old with this one in
"dist" path.

Change Logs


* Print exactaly message when pyarmor couldn't load extension

* Fix problem "version 'GLIBC_2.14' not found"

* Generate "license.lic" which could be bind to fixed machine.


* Add missing extensions for linux x86_64.


* Add command "licene" to generate more "license.lic" by project


* Add information for using registration code


* Add option --with-extension to support cross-platform publish.

* Implement command "capsule" and add option --with-capsule so that we
can encrypt scripts with same capsule.

* Remove command "convert" and option "-K/--key"


* Encrypt pyshield.lic when distributing source code.


* Enhance encrypt algorithm to protect source code.
* Developer can use custom key/iv to encrypt source code
* Compiled scripts (.pyc, .pyo) could be encrypted by pyshield
* Extension modules (.dll, .so, .pyd) could be encrypted by pyshield


* Q: Will the license expire? Is the license the same for develop
machine and target machine?

A: "license.lic" for pyarmor will expired about by the end of next
month. After that, a registration code is required to run

The "license.lic" in the target machine is different from develop
machine, it is generated by pyarmor. Simply to say, "license.lic"
of pyarmor is generated by me, "license.lic" in the target
machine is generated by developer who uses pyarmor.

* Q: If I pay for the registration code, it is valid forever? Or I
have to pay periodically?

A: Forever now.

Known Issues

[Need to document]

Bug reports

Send an email to: ````, Thanks.

More Information

The trial license will be expired in the end of this quarter, after
that, you need pay for registration code from

You will receive information electronically immediately after
ordering, then replace the content of "license.lic" with registration
code only (no newline).

All of these functions are integrated to an IDE tool named as Pyshield
either, for more information to see

Copyright (c) 2009 - 2014 Dashingsoft Corp. All rights reserved.

2014-12-02 09:45 + China Standard Time

Project details

Release history Release notifications

This version
History Node


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Filename, size & hash SHA256 hash help File type Python version Upload date
pyarmor-1.7.6.tar.bz2 (4.3 MB) Copy SHA256 hash SHA256 Source None
pyarmor-1.7.6.tar.gz (5.7 MB) Copy SHA256 hash SHA256 Source None (5.8 MB) Copy SHA256 hash SHA256 Source None

Supported by

Elastic Elastic Search Pingdom Pingdom Monitoring Google Google BigQuery Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN SignalFx SignalFx Supporter DigiCert DigiCert EV certificate StatusPage StatusPage Status page