Windows installation instructions not working on win8 about sulley HOT 15 OPEN

Grr, I've been dreading this ticket.

Anyway, you CAN use the new mingw toolchain, you just need to tweak some source files for it. I got it working at some point and I'll have to go figure out how the hell I did it before.

Leave it to windows to break everything :(. Let me see what I can do with it.

from sulley.

Thanks for the reply and sorry to give you the creeps :P

But for once I think this is not the fault of MS, but the fault of the MinGW devs (at least regarding to the thread I mentioned previously ).

Anyways, I'm awaiting the source code diffs :D (EDIT: just kidding)

from sulley.

Yeah, basically older python modules use a specific flag that is no longer recognized with new versions of mingw, so it kinda freaks out and dies.

Speaking of, Windows 8 is awful. This is an issue that shoud've been fixed a while ago anyway, you shouldn't have to install an old version, so let me think on a better way to tackle that problem in general. I'll probably have to host out the various submodules though this github repo so it'll work.

Hrm...

from sulley.

Multiplatform support seems to be a bugger. :P

Just for clarification: The installation instructions are working on a fresh Win7-VM (after updates)?
That would solve my problem, for the time being.

EDIT: Or would the pragmatic approach be to use a Linux-VM (and if so, which distro would you recommend or is used by the devs, Debian, Ubuntu,...)?

from sulley.

Yessir, everything should work perfect on a win7 vm. That's what I wrote the instructions for.

I'm also going to be re-designing sulley from the bottom up while keeping pretty much only the fuzzing engine itself, it's just easier to re-architect it from the beginning. This release is pretty much only going to be supported for bugfixes until the new version comes out.

from sulley.

Alright, I'll try tomorrow and if everything works I'll post the list of installed updates, etc for future reference (you'll never know. yeah I know, I'm neurotic regarding configs, but that's an occupational disease :P)

from sulley.

Ok, tomorrow was a bit optimistic...

Anyways, now I've tried installing sulley according to the installation instructions on a clean Windows7 VM.
All build commands complete succsessfully, but when I try to verify the installation by executing 'python network_monitor.py' I get the followowing error:

Traceback (most recent call last):
File "network_monitor.py", line 11, in
import pcapy
ImportError: DLL load failed: The specified module could not be found.

EDIT: typos

from sulley.

Ahh, yeah. That's due to a mismatch between 32/64 bit installations. It's
probably better to just use the 32 bit everything, though I have gotten the
64 bit versions of things working fine.

On Sun, Dec 16, 2012 at 11:42 AM, theliberator [email protected]:

Ok, tomorrow was a bit optimistic...

Anyways, now I've tried installing sulley according to the installation
instructions on a clean Windows7 VM.
All build commands complete succsefully, but when I try to veryify the
installation by executing 'python network_monitor.py' I get the followowing
error:

Traceback (most recent call last):
File "network_monitor.py", line 11, in
import pcapy
ImportError: DLL load failed: The specified module could not be found.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/42#issuecomment-11419603.

from sulley.

Is 32/64bit an issue for the python modules or only the installers?

EDIT: Wait,..., I think I have already python 32bit, maybe I should try using the 64bit version of python.

from sulley.

Well the problem comes in when you either install a 32 bit version of python, and 64 bit modules through an MSI, or vice versa. Just make sure you do all of one or all of the other. Any modules you compile yourself also need to be mindful of that (32 bit compiler vs 64 bit compiler).

In the future I'm going to attempt to just include everything myself with a portable version of python since this is such a pain in the ass to manage!

from sulley.

Alright, 64bit python didn't work at all, failed as soon as pydbg!?

I guess I'll have to check everything again regarding 32/64bit.
After (or if) I get things working, I'll put together a .msi-file for conviniency
.

from sulley.

Ok, I've tried to install sulley on a 32-bit Windows 7.

Again everything compiles and installs without any error messages and again I get the error regarding pcapy on running 'python network_monitor.py'.

'pcapy.pyd' and 'pcapy-0.10.5-py2.7.egg-info' are present in 'C:\Python27\Lib\site-packages' and I also added 'C:\Python27\Lib\site-packages' to PYTHONPATH. Still pcapy is not found!?

So, 32/64-bit doesn't seem to be the reason for the error, what else could it be then?

from sulley.

Oooh, I know what's going on.

You're using the unstable branch of Sulley (1.1), yes? Some changes to allow for UDP fuzzing have broken windows functionality, which is why they're not in the master branch.

Master branch should be the good old sulley you know and love.

from sulley.

I'm not quite sure what version I'm using.
I execute the following command to clone the repository 'git clone https://github.com/OpenRCE/sulley.git'

Do I get the master-branch this way, or v1.1? (Sorry, I'm new to using git.)

EDIT: I tried 'git clone https://github.com/OpenRCE/sulley.git -b master', but I still get the pcapy error (both on Win32 and Win64).

from sulley.

Now I got Sulley working properly, AFAIK. At least the network-monitor behaves as expected.
I fixed the issue, by not installing the MinGW-ObjC compiler (as it is described in item 1 of the installation instructions) and installing the MinGw-C++ compiler instead (which also makes a lot more sense to me, because why should pcapy be using ObjC for the Windows version!?).

from sulley.