rlxcrypt
seamlessly encrypt, distribute and load python modules
Usage
you have a .py file that you want to distribute such as
|
+- mymodule.py
+- main.py
and in main.py you use it:
# main.py
import mymodule as m
m.some_func()
to distribute module.py encrypted (in a shell):
> rlxcrypt encrypt mymodule.py
> mv mymodule.py some_private_folder
so you have
|
+- mymodule.pye
+- main.py
and then in main.py
# main.py
import rlxcrypt
import mymodule as m
m.some_func()
Notes
rlxcryptuses RSA encryption as part of the import hooks to detect encrypted files and decrypts them on the fly during the import process.rlxcryptis distributed only as a binary for your architecture, which contains all mechanics to encrypt and decrypt.rlxcryptsources are obfuscated in several custom steps (no public obfuscation library is used) and then compiled into binary code.- it is not 100% bullet proof, it just makes it very hard to crack as it would require to reverse engineer the binary file AND the obfuscation logic.
Metadata
Release files for rlxcrypt 0.0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rlxcrypt-0.0.7-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.17+ x86-64 | Details for rlxcrypt-0.0.7-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| rlxcrypt-0.0.7-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.17+ x86-64 | Details for rlxcrypt-0.0.7-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| rlxcrypt-0.0.7-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.17+ x86-64 | Details for rlxcrypt-0.0.7-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
Total release size: 1.0 MB
Release files / rlxcrypt-0.0.7-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rlxcrypt-0.0.7-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 348.9 kB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
d8ed1dc04aa2e11c8784e40f645eb014d1bde6a6ea5e0a7296c5538f5e28a370
|
|
BLAKE2b-256 checksum How to use checksums |
f8c7c89504a3d1cdab588d1d63791e26b64e8f2de211430a2375369523bef186
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / rlxcrypt-0.0.7-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rlxcrypt-0.0.7-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 350.6 kB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
18e5e83b8ca775bc4956ef371bbc2b41e8b82a2a83db4d34c9a9dbdba2f74cf7
|
|
BLAKE2b-256 checksum How to use checksums |
a72f17b13831d3a12b2cb61fed59c4a7ddfcd6723b9f8789233ae0c0b22545e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / rlxcrypt-0.0.7-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | rlxcrypt-0.0.7-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 325.3 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
73e196297d76163b73722ad8379b780b715e3a02e2c5baf136a812ed5696cc65
|
|
BLAKE2b-256 checksum How to use checksums |
191b13714377b81f9a4bc79574328711aeaf3844ca7711ad8d36c05d7bcca09a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for rlxcrypt 0.0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.