![]() Wine32 “C:\\Python27\\python.exe” /usr/share/pyinstaller/pyinstaller.py /tmp_my_script.pyĪnd that was it… everything compiled and ready to roll…. So then it was a simple thing to emulate them… like so: Digging into the source code… it uses wine to call the windows version of python, and runs pyinstaller under the wine environment. exe files and is a python framework… and research confirmed it uses PyInstaller in the background to generate these EXEs. Then I remembered that the VEIL framework on my Kali Linux box generates. I also went down the MinGW route, only to be frustrated by another missing DLL (“msvcr71.dll is missing”) The usual pip install module_name was a frustrating experience on windows (oh how I miss linux in times like this…) and I continuously hit the vcvarsall.bat error, even after installing Visual Studio express 2008, and the “Microsoft Visual C Compiler for Python 2.7”. Output running pyinstaller on Windows > pyinstaller app.py 388 INFO: PyInstaller: 4.7 388 INFO: Python: 3.7.6 389 INFO: Platform: Windows-10-0-SP0. ![]() But then I started running into problems with modules…. To fully appreciate PyInstaller’s power, it’s useful to revisit some of the distribution problems PyInstaller helps you avoid. ![]() I was trying to build my own malicious file… Since I love python, it was natural for me to go down the python pyinstaller route. Initially, I coded everything on windows, downloaded and installed PyInstaller on windows, and attempted to use the usual pyinstaller -F my_script.pyto build my executable. PyInstaller gives you the ability to create a folder or executable that users can immediately run without any extra installation. ![]()
0 Comments
Leave a Reply. |