This is not a suggestion, but it concerns DFind

I'd like to know if your latest versions are still based on the old sfind.

Will you ever release the source code of the old DFind or the new one.

If you won't..

Do you have the SFind source with English/French/whatever (as long as it's not Asian) comments. Because I would certainly appreciate it if you wanted to share that.


Spook

nop its no more based on sfind, because there is in the old sfind 1 function for each scanners which make the scan too big at this step and too long to update.
The way I took to build the new one is to use only 3 functions for all scanners, I mean , a main to handle all cmdlines, an engine1 wich handles all ports , ip , etc datas settings and also loading of the threads, and the theard function handles all fucntion runned by the threads (the main scanning engine if you want)

All this allow me to quickly update all scanners at the same time(because they are using the sames functions) and to not get bored by updating it because all reside in one c code :) The main problem is if im doing a code error , I can break all scanners :p

and no I wont share it , maybe some part of it , dunno , keep the board in your bookmarks, there is always miracles ;)

and btw when I say there is only 3 engines wich handle all scanners,

main:

handles all cmdlines


engine1:

CWinThread1 => when you are using portrange scanner
CWinThread2 => when you are using multiple ports
CWinThread3 => when you are using the simple ip range scanner
(all that with a good loop is enough to add the number of scanners that you want without having to add more thread calls)

engine2:

execution of the loaded threads depending of your cmdline



no more functions or thread calls than this make it so small ;)

and btw when I say there is only 3 engines wich handle all scanners,

main:

handles all cmdlines


engine1:

CWinThread1 => when you are using portrange scanner
CWinThread2 => when you are using multiple ports
CWinThread3 => when you are using the simple ip range scanner
(all that with a good loop is enough to add the number of scanners that you want without having to add more thread calls)

engine2:

execution of the loaded threads depending of your cmdline



no more functions or thread calls than this make it so small ;)


This seems to be more logical too..

I just started C and source code would certainly help me understand how a scanner works. It'll probably take some time before I'm gonna be able to create one but I'll get there :P


Yes, I'll keep this in my bookmarks.. I don't register for not using my account afterwards ;)

Spook

I recommand you a book to starts learning C, maybe old (around 1990, daddy's book :D )
but enough small (280 pages) and nicely wrote with code examples etc to learn fastly:

"The C PROGRAMMING LANGUAGE 2nd Edition"

in french called:

"Le Langage C"

http://www.linuxfocus.org/common/images/DennisRitchie.gif
the man who was one of the developers of C and Unix.

Thanks, I found at my local shop :)


I had this "C reference guide" too, but it's a bit hard when it's all in English (as I'm not English)

yep I have the french version me, look around maybe it has been translated in your langage so.

yep I have the french version me, look around maybe it has been translated in your langage so.


Already found it in my language :)

The old version and even an updated version which will be released on 29/06/2005 :lol:


Thanks again for your help