Open Toma400 opened 2 years ago
Most obfuscators already are reverse-engineered, what you could do is release versions in a binary file (using PyToExe for example). Which would be easier for users and also safer code-wise
Look at this repo https://github.com/u0pattern/PyArmor-Deobfuscator for example
@gingernikki thanks for your comments ^^ honestly I'm not even sure now if I need to obfuscate code, given how fast whole development process goes, but if I ever come back to this, I will definitely look into your suggestion
The only thing I was pretty scared about obfuscating in general was that it would make me get rid of build file which I really care about 🥺 I mean, I created it a while ago, but I so love how pyInstaller is utilised with it, it's so simple and allow for a lot of customisations (and in general I don't like switching from something which works, into something I don't know much about)
There should be - at least temporar - obfuscation for the code of Librerian, at least until it goes open source. This is because there can be stealers here and there, and this project is a bit too precious for me to let ppl loosely steal.
I'd suggest this module as found thanks to this stackoverflow topic.
PyArmour has cool name and seems to easy to un-bind code from when I will go to open source later.