On 3/16/2009 6:56 PM, [email protected] wrote: > > > On Mar 17, 12:38 am, Giovanni Bajo <[email protected]> wrote: >> It works already if you enable it in the Configure.py (and/or maybe >> something commented out in Makespec.py, I can't recall right now). >> >> The only issue is that it's pretty useless as-is, because it simply >> requires you to generate a key, and pass it within the spec file; then >> it encrypts the whole file with this key *and* store it within the file >> in some scrambled manner. > > encrypts the bytecodes?
Yes. >> In other words, I don't see anyone using it as-is. But if it's enough >> for you, you're welcome to use it. >> -- >> Giovanni Bajo >> Develer S.r.l.http://www.develer.com > > Yes, It's enough for me as long as it adds some level of protection to > the code. May i ask, what is "enough" for you? What other technique > can we do to harden the encryption? It would be better if there was a way to inject the encryption key from the outside, instead of storing it within the executable. Anyway, we shouldn't get too complicated with this, because it does not make much sense when there are professional programs for software protection. -- Giovanni Bajo Develer S.r.l. http://www.develer.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/PyInstaller?hl=en -~----------~----~----~----~------~----~------~--~---
