Pyarmor

Latest version: v9.0.5

Safety actively analyzes 682244 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 25 of 45

5.6.0

Not secure
In this version, new `private capsule`, which use 2048 bits RSA key to improve security for obfucated scripts, is introduced for purchased users. All the trial versions still use one same `public capsule` which use 1024 bits RSA keys. After purchasing PyArmor, a keyfile which includes license key and `private capsule` will be sent to customer by email.

For the previous purchased user, the old private capsules which are generated implicitly by PyArmor after registered PyArmor still work, but maybe not supported later. Contact jondy.zhaogmail.com if you'd like to use new `private capsule`.

The other changes:

* Command `register` are refined according to new private capsule

**Upgrade Note for Previous Users**

There are 2 solutions:

1. Still use old license code.

It's recommanded that you have generated some customized "license.lic" for the obfuscated scrips and these "license.lic" files have been issued to your customers. If use new key file, all the previous "license.lic" does not work, you need generate new one and resend to your customers.

Actually the command `pip install --upgrade pyarmor` does not overwrite the purchased license code, you need not run command `pyarmor register` again. It should work, you can check it by run `pyarmor -v`.

Or in any machine in which old version pyarmor is running, compress the following 2 files to one archive "pyarmor-regfile.zip":

* license.lic, which locates in the installed path of pyarmor
* .pyarmor_capsule.zip, which locates in the user HOME path

Then register this keyfile in the new version of pyarmor

pyarmor register pyarmor-regfile.zip

2. Use new key file.

It's recommanded that you have not yet issued any customized "license.lic" to your customer.

Forward the purchased email received from MyCommerce to jondy.zhaogmail.com, and the new key file will be sent to the registration email. If pyarmor license is purchased after 2017-10-10, no fee for this upgrading. Before 2017-10-10, please purchase a new license for latest pyarmor.

5.5.7

Not secure
* Fix webui bug: raise "name 'output' is not defined" as running `packer`

5.5.6

Not secure
* Add new restrict mode 2, 3 and 4 to improve security of the obfuscated scripts, refer to :ref:`Restrict Mode`
* In command `obfuscate`, option `--restrict` supports new value 2, 3 and 4
* In command `config`, option `--disable-restrict-mode` is deprecrated
* In command `config`, add new option `--restrict`
* In command `obfuscate` the last argument could be a directory

5.5.4

Not secure
* Fix issue: the output path isn't correct when building a package with multiple entries
* Fix issue: the obfuscated scripts raise SystemError "unknown opcode" if advanced mode is enabled in some MacOS machines

5.5.3

Not secure
* Fix issue: it will raise error "Invalid input packet" to import 2 independent obfuscated packages in 64-bit Windows.

5.5.2

Not secure
* Fix bug of command `pack`: the obfuscated modules aren't packed into the bundle if there is an attribute `_code_cache` in the `a.pure`

Page 25 of 45

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.