Hello,

I'm going to work on implementing crypting support for the packaged
executable. The idea is that the .pyc files will be crypted with a simmetric
cipher (say, Rijndael/AES) and the bootloader will use an external key to
decrypt and run the executable. Fair warning: I'm *no* crypt expert.

Open issues (suggestions are welcome):

- How key feeding should work? My current plan is to require a file called
"executablename.key" in the same directory of the executable, containing the
key in a text format (it's going to be 128/192/256 bits, or so). I was
thiking of something like a .ini format. Of course, users can always
customize the bootloader themselves for specific uses, so I'm just looking
for a generic good-enough solution. Also additional program-specific
information can be stored in the .ini file.

- Should we crypt only .pyc/.pyo files or also .pyd/.so/.dll? Besides speed
issues which I don't consider very important (since block ciphers are pretty
fast), I am a little worried about secutiry holes. The plaintext version of
most binary files could be easily found (say, all the standard modules
shipped with Python) so this could compromise the key. Maybe this could be
made an option.

-- 
Giovanni Bajo

_______________________________________________
PyInstaller mailing list
PyInstaller@lists.hpcf.upr.edu
http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller

Reply via email to