- #OBSCURE 2 PC KICKASS HOW TO#
- #OBSCURE 2 PC KICKASS CRACKED#
- #OBSCURE 2 PC KICKASS SKIN#
- #OBSCURE 2 PC KICKASS SOFTWARE#
- #OBSCURE 2 PC KICKASS CODE#
$ pyminifier -nonlatin -replacement-length=50 /tmp/tumult.py
#OBSCURE 2 PC KICKASS CODE#
The example code looks pretty nasty for casual reverse engineering.
Have you had a look at pyminifier? It does Minify, obfuscate, and compress Python code. This cannot be done if you're using LGPL code though. That way, it'd sure be difficult to intercept calls to/from python and whatever framework libraries you use. You might be able to build a single executable if you can link to (and optimize with) the python runtime and all libraries (dlls) statically. That way, your Python module is pretty monolithic and difficult to chip at with common tools. You could probably get Cython to store the C-files separately for each module, then just concatenate them all and build them with heavy inlining.
#OBSCURE 2 PC KICKASS HOW TO#
See This Blog Post (not by me) for a tutorial on how to do it. We're already building some thirdparty libs as pyd/dlls, so shipping our own python code as binaries is not a overly big step for us.) (I'm actually considering this for our product. (.NET or Java less safe than this case, as that bytecode is not obfuscated and can relatively easily be decompiled into reasonable source.)Ĭython is getting more and more compatible with CPython, so I think it should work. your employer) could expect from regular Code, I think. That way, no Python (byte) code is left and you've done any reasonable amount of obscurification anyone (i.e.
#OBSCURE 2 PC KICKASS SKIN#
Use Cython, Nuitka, Shed Skin or something similar to compile python to C code, then distribute your app as python binary libraries (pyd) instead.
Maybe it's time to consider to go with the flow. You cannot copy a service, pirate nor steal it. Nowadays, business models tend to go for selling services instead of products. Therefore, it's just a casual legal issue. You cannot prevent somebody from misusing your code, but you can easily discover if someone does. Having a legal requirement is a good way to go
#OBSCURE 2 PC KICKASS CRACKED#
Newer versions of Windows are cracked every time. You can analyze obfuscated PHP, break the flash encryption key, etc. Obfuscation is really hardĮven compiled programs can be reverse-engineered so don't think that you can fully protect any code. This is not a bad thing, it is important that several different tools exist for different usages. If you want something you can't see through, look for another tool. It's the contrary everything is open or easy to reveal or modify in Python because that's the language's philosophy. You must use the right tool to do the right thing, and Python was not designed to be obfuscated.
#OBSCURE 2 PC KICKASS SOFTWARE#
This is cruel, and will give you a bad reputation, but it certainly makes your software stop working. Offer customization at rates so attractive that they'd rather pay you to build and support the enhancements. This can be carried to absurd extremes, but you should offer new features that make the next release more valuable than reverse engineering. When the next release breaks their reverse engineering, there's no point. Offer upgrades and enhancements that make any reverse engineering a bad idea. Make your product slightly less expensive. If your stuff is so good - at a price that is hard to refuse - there's no incentive to waste time and money reverse engineering anything. Also, some open-source licenses prohibit you from concealing the source or origins of that component. Note that some of your Python-based components may require that you pay fees before you sell software using those components. This still works even when people can read the code.
Since no technical method can stop your customers from reading your code, you have to apply ordinary commercial methods. And that's in spite of the DMCA making that a criminal offense. Even the firmware on DVD machines has been reverse engineered and the AACS Encryption key exposed. Nothing can be protected against reverse engineering. "Is there a good way to handle this problem?" No.
0 kommentar(er)
