6.1. Asking questions in GitHub¶
Before ask question, please try these solutions:
- If using pyarmor-7 or Pyarmor < 8.0, please check Pyarmor 7.x Doc
- Check the detailed table of contents
- If you have not read Getting Started, read it
- Check Error Messages
- If you have trouble in pack, check Insight Into Pack Command
- If you have trouble in RFT Mode, check Using rftmode pro
- If you have trouble in BCC Mode, check Using bccmode pro
- If you have trouble with third-party libraries, check Work with Third-Party Libraries
- If it’s related to security and performance, check Security and Performance
- Look through this page
- Enable debug mode and trace log, check console log and trace log to find more information
- Make sure the scripts work without obfuscation
- Do a simple test, obfuscate a hello world script, and run it with python
- If not using latest Pyarmor version, try to upgrade Pyarmor to latest version.
- Search in the Pyarmor issues
- Search in the Pyarmor discussions
Please report bug in issues and ask questions in discussions
When report bug in issues, please copy the whole command line pyarmor gen and first 4 lines in the console, do not mask version and platform information, and do not paste snapshot image:
$ pyarmor gen -O dist --assert-call foo.py INFO Python 3.10.0 INFO Pyarmor 8.1.1 (trial), 000000, non-profits INFO Platform darwin.x86_64
6.2. Segment fault in Apple¶
Generally it’s code sign issue
If segment fault when obfuscating scripts or registering Pyarmor, try to re-sign extension
$ codesign -s - -f /path/to/lib/pythonX.Y/site-packages/pyarmor/cli/core/pytransform3.so
If segment fault when launching obfuscated scripts, try to re-sign extension
$ codesign -s - -f dist/pyarmor_runtime_000000/pyarmor_runtime.so
If your app doesn’t have the new signature format, or is missing the DER entitlements in the signature, you’ll need to re-sign the app on a Mac running macOS 11 or later, which includes the DER encoding by default.
If you’re unable to use macOS 11 or later to re-sign your app, you can re-sign it from the command-line in macOS 10.14 and later. To do so, use the following command to re-sign the MyApp.app app bundle with DER entitlements by using a signing identity named “Your Codesign Identity” stored in the keychain:
$ codesign -s "Your Codesign Identity" -f --preserve-metadata --generate-entitlement-der /path/to/MyApp.app
Refer to Apple official documentation Using the latest code signature format
Using otool and install_name_tool to fix Python library issue
pyarmor_runtime.so need Python shared library, if there is no found Python shared library, it may crash. To display the names and version numbers of the shared libraries that the object file uses:
$ otool -L /path/to/lib/python3.9/site-packages/pyarmor/cli/core/pytransform3.so /path/to/lib/python3.9/site-packages/pyarmor/cli/core/pytransform3.so: pytransform3.so (compatibility version 0.0.0, current version 1.0.0) @rpath/lib/libpython3.9.dylib (compatibility version 3.9.0, current version 3.9.0) ...
rpath is configured by:
$ install_name_tool -id pytrnsform3.so \ -change $deplib @rpath/lib/libpython$ver.dylib \ -add_rpath @executable_path/.. \ -add_rpath @loader_path/.. \ -add_rpath /System/Library/Frameworks/Python.framework/Versions/$ver \ -add_rpath /Library/Frameworks/Python.framework/Versions/$ver \ build/$host/libs/cp$ver/$name.so
So check there is
@rpath/lib/libpython3.9.dylib. If it doesn’t exists, please adapt to current Python by using
install_name_tool. Suppose current Python shared library is
$ install_name_tool -change @rpath/lib/libpython3.9.dylib /usr/local/Python.framework/Versions/3.9/Python \ /path/to/lib/pythonX.Y/site-packages/pyarmor/cli/core/pytransform3.so
How to find current Python shared library, please search network to find answer. Note that some Python may not built with shared library, it can’t work with Pyarmor, please rebuild Python with shared library to fix this kind of issue.
It’s same for
Refer to Apple official documentation Run-Path Dependent Libraries
If there are many same version Python installed, make sure pytransform3.so or pyarmor_runtime.so links to the right one
Pyarmor uses JIT to improve security, In Apple M1, it need extra entitlements. Check Python entitlements:
$ codesign -d --entitlements - $(which python)
Refer to Apple official documentation Allow Execution of JIT-compiled Code Entitlement
Check system segment fault log, and search solution by error message
In the old pyarmor 7, I’m using “pyarmor pack …”, I could not find any relate information for this in the pyarmor 8.2. How to solve this?
There is no identical pack in Pyarmor 8, Pyarmor 8+ only provide repack function to handle bundle of PyInstaller. Refer to basic tutorial, topic insight into pack and this solved issue Pyarmor pack missing in pyarmor 8.0
I am interested to know if the users are entitled to updates to ensure compatibility with future versions of Python.
No. Pyarmor license works with current Pyarmor version forever, but may not work with future Pyarmor version. I can’t make sure current Pyarmor version could support all the future versions of Python, so the answer is no.
we use Docker to build/obfuscate the code locally then publish the Docker file to the client. After the build stage, the whole environment (and the license) is gone. I wonder how the workflow would be? Can I add the license file to the pipeline and register every time and build?
It’s no problem to run Pyarmor in Docker or CI pipeline to obfuscate application. Each build registering pyarmor with
pyarmor-regfile-xxxx.zipwhich is generated in initial registration. But It’s not allowed to distribute package pyarmor and Pyarmor Basic, Pyarmor Pro, Pyarmor Group License to customer, and don’t run too many build dockers.
We are currently using a trial license for testing, but unfortunately our scripts are big and we are not able to statistically test the operation of Pyarmor. Do you have a commercial trial license for a certain trial period so that we can test the operation of Pyarmor for our scripts?
Sorry, Pyarmor is a small tool and only cost small money, there is no demo license plan.
Most of features could be verified in trial version, other advanced features, for example, mix-str, bcc mode and rft mode, could be configured to ignore one function or one script so that all the others could work with these advanced features.
Is the Internet connection only required to generate the obfuscated script? No internet connection is required on the target device that uses such script?
No internet connection is required on target device.
Pyarmor has no any control or limitation to obfuscated scripts, the behaviors of obfuscated scripts are totally defined by user.
Please check Pyarmor EULA 3.4.1
Our company has a suite of products that we offer together or separately to our clients. Do we need a different license for each of them?
For a suite of products, if each product is different totally, for example, a suite “Microsoft Office” includes “Microsoft Excel”, “Microsoft Word”, each product need one license.
If a suite of products share most of Python scripts, as long as the proportion of the variable part of each product is far less than that of the common part, they’re considered as “one product”.
If each product in a suite of products is functionally complementary, for example, product “Editor” for editing the file, product “Viewer” for view the file, they’re considered as “one product”
If we buy version 8 license, is it compatible with earlier versions like 6.7.2?
No. Pyarmor 8 license can’t be used with earlier versions, it may report HTTP 401 error or some unknown errors.
Can we obfuscate our code base with the same level as current? (we are obfuscating our code using super plus mode (”–advanced 5”). Is that available on Pyarmor Basic?
The old license is valid for ever. In this case need not upgrade old license to Pyarmor Basic license, just install Pyarmor 8.x, and using pyarmor-7 with old license.
Check License Types for more information about upgrading
If we upgrade the old license, will the current license expire? (no more available in terms of Pyarmor v7?
If upgrade old license to any Pyarmor 8 license, the current license is no more available in the terms of Pyarmor 7.
How long is the current license valid? Is there a published end-of-support schedule?
The license is valid for ever with Pyarmor version when purchasing this license, but may not work for future Pyarmor, there is no schedule about in which version current license doesn’t work.
Since the first release Pyarmor changed its license 3 times
- the initial license issued around year 2010 (I forget the exact date)
- the second license issued on 2019-10-10
- this is the third license, issued on 2023-03-10.
How to refund my order?
If this order isn’t activated and in 30 days since purchasing, you can refund the order by one of ways
- Email to Ordersupport@mycommerce.com with order information and ask for refund.
- Or click FindMyOrder page to submit refund request
What is the ECCN or rating of Pyarmor (EAR99,5D99S,5D002 or other type ECCN)?
Does Pyarmor contain any encryption capabilities?
Pyarmor uses AES/RSA etc., but it hasn’t its own encryption algorithms.
What is the country of origin of this package?
Where is the final built for Pyarmor?
All of Pyarmor packages are published in the PyPI, refer to Pyarmor Package and section Installation in offline device in the chapter <tutorial/installation