BNCSUtil 1.3.2? Been on my mind for awhile

[Sorc.Polgara]

Bleh, I've been looking through iago's lockdown code and it looks like I'm stuck until I can figure out how to port various windows API (i.e. LoadLibrary) and such to Linux.

dlopen is the equivalent function to LoadLibrary, if that helps at all...

If it was merely the task of finding the Linux equivalent APIs, then I wouldn't be having a problem.  I don't believe one can just use the linux equivalent API to load a Windows PE DLL... I wish it were that simple.

Anyways, the BNCSutil source includes some functionality for using PE formatted files which I'm playing around with.  Although I'm unsure if it's robust enough at the moment, since the lockdown checkrevision is much more involved.

[MyndFyre]

rob released his source code for lockdown which implemented the functionality necessary for reading PE files I believe.

Also, K, your email is hidden in your profile.  PM me?

[brew]

Bleh, I've been looking through iago's lockdown code and it looks like I'm stuck until I can figure out how to port various windows API (i.e. LoadLibrary) and such to Linux.

dlopen is the equivalent function to LoadLibrary, if that helps at all...

If it was merely the task of finding the Linux equivalent APIs, then I wouldn't be having a problem.  I don't believe one can just use the linux equivalent API to load a Windows PE DLL... I wish it were that simple.

Whoops, forgot about that.

What's stopping you from just opening it as a regular file?

[Sorc.Polgara]

rob released his source code for lockdown which implemented the functionality necessary for reading PE files I believe.

Also, K, your email is hidden in your profile.  PM me?

Ah, nice, thanks. Yeah, rob's source is much more Linux friendly than iago's source which is what I was using previously.

[Joe[x86]]

iago uses exclusively Linux. His code isn't Linux friendly?

[MyndFyre]

x86] link=topic=17567.msg179031#msg179031 date=1216733556]
iago uses exclusively Linux. His code isn't Linux friendly?

iago's lockdown code was written in Visual Studio 2005 and was targeted for Windows.

[vector]

Either way, once you can get the original source to compile in windows, then you know that's a dependable source to work on.

So what kinds of things are you guys dealing with to make it compatible with the new lockdown algorithm?

[Joe[x86]]

x86] link=topic=17567.msg179031#msg179031 date=1216733556]
iago uses exclusively Linux. His code isn't Linux friendly?

iago's lockdown code was written in Visual Studio 2005 and was targeted for Windows.

Oh. I'm dumb.

[Mystical]

Has anyone updated this for lockdown?

Some of the links previously posted for the source in this topic don't seem to be working.

[l)ragon]

lol the project die?
hows it coming along.

[c0ol]

I am currently working on this library in an effort to improve some problems I am having with it.  Here is a tenative list of my goals right now and where I stand on them, I started this a few days ago.  1-5 is my progress

4 - 1 ) Remove C++ requirements from all project source
5 - 2 ) Build with MinGW on windows vista
2 - 3 ) Normalize APIs, add prefixes to names, streamline function names
5 - 4 ) Separate PE into its own library
3 - 5 ) Remove unessary win32 calls
2 - 6 ) Rewrite some of the functions to be more in-line with my new style
0 - 7 ) Implement fully doxygen coverage
2 - 8 ) Implement a high level of unit test coverage using cuint
0 - 9 ) Use CMake instead of auto-terrible
1 - 10) Add functionality required to pass Warden and Lockdown challenges

[vector]

I am currently working on this library in an effort to improve some problems I am having with it.  Here is a tenative list of my goals right now and where I stand on them, I started this a few days ago.  1-5 is my progress

4 - 1 ) Remove C++ requirements from all project source
5 - 2 ) Build with MinGW on windows vista
2 - 3 ) Normalize APIs, add prefixes to names, streamline function names
5 - 4 ) Separate PE into its own library
3 - 5 ) Remove unessary win32 calls
2 - 6 ) Rewrite some of the functions to be more in-line with my new style
0 - 7 ) Implement fully doxygen coverage
2 - 8 ) Implement a high level of unit test coverage using cuint
0 - 9 ) Use CMake instead of auto-terrible
1 - 10) Add functionality required to pass Warden and Lockdown challenges

That's quote a lot... Don't freakin change the function names inside the DLL, or all current bots that use it will not be able to use this version..

I assume you know this already.