| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 268 |
| Technical Name |
ylhc_odoo_encryptor |
| License | OPL-1 |
| Website | https://www.ylhctec.com |
| Versions | 15.0 16.0 17.0 18.0 19.0 |
Odoo Module Encryption Tool
Background and Introduction
In Odoo development, encryption is often necessary, especially for product-type modules. For project-type modules, this is less of a concern. The main issues are:
- How to provide trial versions without encryption
- What to do if clients don't pay after online deployment
- How to distribute at low prices without encryption (open source is not suitable for low-price distribution)
Odoo Encryption Tool Interface
The core principle is to convert Python code to C++ code, then compile the cpp into a whl package. The whl package consists of dll or so files. This way, users receive the final module as binary files, effectively limiting code leakage.
Tool Features
- Convenient Operation: Simply select the directory to encrypt
- Flexible: Each file can be chosen to encrypt or not. In most cases, hiding core content is sufficient. Over-encryption can cause inconvenience for team collaboration
Usage Steps
- Select the source module directory
- Select the target directory (where the final output will be generated)
- Click encrypt - the program will encrypt the module and generate two outputs: an encrypted Odoo module and a whl package project
The original module code will be replaced. Files that don't need encryption can be manually restored, providing sufficient flexibility.
As shown in the image, the final code calls library functions. The generated cpp code is also shown in the image.
After module generation, it still needs to be compiled into a whl package. Enter the whl project directory and run:
python setup.py bdist_wheel
Generate the wheel package. Note that pybind11 needs to be installed via the command: pip install pybind11. The final generated package can then be copied to the client machine for installation.
However, due to different operating systems and Python versions, compiling this way becomes very cumbersome. Therefore, the generated project supports CI compilation, which can generate packages for different platforms and Python versions, and automatically push them to PyPI. Users can then directly install with pip install ylhc_reading_base, making it nearly seamless for users with excellent platform compatibility.
Usage Instructions
To use this encryption tool, please follow these steps:
- Run the
encrypt_client.exefile located in the module's encryptor directory - Platform Support: Currently only supports Windows platform
- First-time Use: Contact us to obtain the registration code for first-time activation
Important Notice
For first-time use, please contact us to obtain the registration code.
Contact WeChat: masterjmz
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module