I have been working on an OSI(Open Source intelligence) tool for a while, i was wondering if anyone would be interested in porting this over into assembly, so as to stream line it. i would be willing to part ways with it, as long as you would be willing to on occasion give me any updated code you use (Looking for new ideas).
www.youtube.com/watch?v=NcishPg4B-s <--- a video of the tool (old email was worshipped@yahoo I'm not narcissistic lulz)
(PM me if interested)
I am continuing to work on the project and incorporate more methods of associating/refining the data
The version in the video is about 3-4 compiles behind my new one.
Sorry if I committed any transgressions with the mood and information in this post.
www.youtube.com/watch?v=NcishPg4B-s <--- a video of the tool (old email was worshipped@yahoo I'm not narcissistic lulz)
(PM me if interested)
I am continuing to work on the project and incorporate more methods of associating/refining the data
The version in the video is about 3-4 compiles behind my new one.
Sorry if I committed any transgressions with the mood and information in this post.
What advantage do you expect to get from porting the tool to assembly?
Only watched ~40 seconds of the video... too much Hollywood hacker-tool look to it, ick.
Only watched ~40 seconds of the video... too much Hollywood hacker-tool look to it, ick.
What advantage do you expect to get from porting the tool to assembly?
Yea, I was wondering about that...
Seems that this tool will be limited by the network speed?
At any rate, I suppose with both size and speed, you can get a long way by just optimizing C++ code.
What language is it written in currently, and what exactly are the bottlenecks you were hoping to fix by using assembly?
well i wanted to port the methods over, it's in vb6 but only because of the ability to easily use browser objects to emulate user driven searches/bypass sec features, that limit most 'bot like' applications. as well as having it in asm would give it true portability.
If you want portable, asm is not the way. Different OSes often don't even have the same assembly syntax, so you can't even assemble your sourcecode (eg masm vs nasm/gas etc). And then we don't even get into all the OS-specific API calls and other things. Not to mention different types of x86... a 32-bit x86 source won't work on a 64-bit x64 OS. You'd need to rewrite nearly everything.
If you want portable, you should keep things ANSI C, or simplified C++, and use standardized libraries wherever possible (libc, STL, POSIX, etc).
Even so, having a GUI would make it hard to keep it portable. A framework like Qt may help there. But if you also want to use a browser object, it's going to be even more difficult.
If you want portable, you should keep things ANSI C, or simplified C++, and use standardized libraries wherever possible (libc, STL, POSIX, etc).
Even so, having a GUI would make it hard to keep it portable. A framework like Qt may help there. But if you also want to use a browser object, it's going to be even more difficult.