Windows 7 - Fresh out the Box - Part 2!
Well, fighting with Windows is bluntly annoying. I've been researching debugging, python, ctypes, and various other tools used for reverse engineering, malware analysis, and exploit development. attempting to install
Immunity-Debugger which requires
Python to run correctly and the folks over at Immunity have bundled the install together rather effortlessly. Props!
On the flip side, the research of the 32 bit architecture requires analysis and examination from both Winblows and Linux. Upon installing Immunity-debugger for Winblows, I proceeded to double click the executable unprepared for the time travel to a parallel dimension of pist off I've never adventured to.
Rather than redeeming my ticket for my trip and getting my time, effort, and sanity back, I decided to trouble-shoot. Windows decided it had beef with the python27.dll file. Apparently this .dll decided to play hide and seek today in Windows land, which kind of reminds me a Pink Floyd song...
After some research, corrupted system files, sfc /scannow, several reboots, regsvr32, and many failed installations later I tried to install a different/newer/stable version of python (3.2.2). I noticed during the installation the python installation asks the end user if you'd like to install for everyone or just me. Well, considering the fact I'm a security savvy kinda guy I decided maybe not everyone should have access to the suite/tool I'm using to find vulnerabilities and write exploits.
Instead of displaying some type of useful output, let's get ready for a fun game of name that error. Changing the file permissions on the file doesn't appear to the fix the issue and registering the .dll doesn't either. How about an un-install of python and allow access to your installation to everyone.
Microsoft, I knew you had a fix..
To be continued..
