+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Software Development (https://hackforums.net/forumdisplay.php?fid=118)
+---- Thread: [C#] NetCrack || Free MD5 Cracker || Use your clients to crack hashes (/showthread.php?tid=4838337)
Pages: Pages
1
2
NetCrack || Free MD5 Cracker || Use your clients to crack hashes - BahNahNah - May 26, 2015
The more clients you have the quicker it will crack the hash.
The stub is .net 2.0 dependant.
This is using the eSock class
Screenshot:
Spoiler (Click to View)
![[Image: bKMX1h3.png]](https://i.imgur.com/bKMX1h3.png)
Stub output:
Spoiler (Click to View)
Download: [Source] [Binary]
* - Only3 - May 26, 2015
(May 26, 2015 10:27 PM)BahNahNah Wrote: The more clients you have the quicker it will crack the hash.
...
how its more quick i guess u send to all the clients the same chars so all do the same
* - BahNahNah - May 26, 2015
(May 26, 2015 10:40 PM)Only3 Wrote: how its more quick i guess u send to all the clients the same chars so all do the same
Each client does a block. Its a bit hard to explain but each block is different, so clients arnt doing the same work as another client.
It could be quicker by sending a client multiple blocks, but i was too lazy.
* - Only3 - May 26, 2015
if so u have brain not that its new but good thing to code
* - BahNahNah - May 27, 2015
(May 26, 2015 10:53 PM)Only3 Wrote: if so u have brain not that its new but good thing to code
Thanks?
Spoiler (Click to View)
* - CodeAssassin - May 27, 2015
(May 27, 2015 12:38 AM)BahNahNah Wrote: Thanks?
Spoiler (Click to View)
I'm pretty sure he means even tho this is not a new idea at least you coded something of worth. Rather then the shit I have been outputting recently lol.
Good job mate this looks cool. Will Deffo check out your sauce :)
* - BahNahNah - May 27, 2015
(May 27, 2015 01:34 AM)sweetysuckscock Wrote: I'm pretty sure he means even tho this is not a new idea at least you coded something of worth. Rather then the shit I have been outputting recently lol.
Good job mate this looks cool. Will Deffo check out your sauce :)
Do you know a better way to keep the stub open?
My current method: (i know its bad)
Code
while(true)
{
Thread.Sleep(1000000);
}* - CodeAssassin - May 27, 2015
(May 27, 2015 01:39 AM)BahNahNah Wrote: Do you know a better way to keep the stub open?How about a simple bool = false,
My current method: (i know its bad)
Codewhile(true)
{
Thread.Sleep(1000000);
}
Set to true when the jobs complete and shut task after. Tbh I am on phone so can't check it out just yet. I'll get up download and have a look to see buddy :)
Can you not have a property(bool) in the connect class and the while true where it is empy(no thread.sleep) and just set to true when your operation is finished?
Apart from that would need to do some testing, This looks great btw, nice use of your esocks class :D
* - BahNahNah - May 27, 2015
(May 27, 2015 01:50 AM)sweetysuckscock Wrote: How about a simple bool = false,
Set to true when the jobs complete and shut task after. Tbh I am on phone so can't check it out just yet. I'll get up download and have a look to see buddy :)
Can you not have a property(bool) in the connect class and the while true where it is empy(no thread.sleep) and just set to true when your operation is finished?
Apart from that would need to do some testing, This looks great btw, nice use of your esocks class :D
The stub stays connected (or tries to be) to the server all the time.
Using just a while(true) loop would use too much cpu.
* - CodeAssassin - May 27, 2015
(May 27, 2015 02:29 AM)BahNahNah Wrote: The stub stays connected (or tries to be) to the server all the time.
Using just a while(true) loop would use too much cpu.
Hmm. What about in the while loop making it run some small operation constantly like. Get it to find it's own process in the taskmanager and just making it loop forever check if it's there in a using statement of course to keep the mem down. Else not really sure what you could run. I see your issue now you need it connected constantly.
* - BahNahNah - May 27, 2015
(May 27, 2015 02:53 AM)sweetysuckscock Wrote: Hmm. What about in the while loop making it run some small operation constantly like. Get it to find it's own process in the taskmanager and just making it loop forever check if it's there in a using statement of course to keep the mem down. Else not really sure what you could run. I see your issue now you need it connected constantly.
Wouldn't that also use high resources?
There must be a better way of doing it, how do rat stubs stay open?
* - CodeAssassin - May 27, 2015
(May 27, 2015 03:06 AM)BahNahNah Wrote: Wouldn't that also use high resources?
There must be a better way of doing it, how do rat stubs stay open?
Got one solution add a reference to Windows.forms and
Code
System.Windows.Forms.Application.Run()You're welcome :)
* - AlphaDelta - May 27, 2015
(May 27, 2015 03:06 AM)BahNahNah Wrote: Wouldn't that also use high resources?
There must be a better way of doing it, how do rat stubs stay open?
Choke the main thread, something like
PHP Code
<?php
while(running) Thread.Sleep(100);
(May 27, 2015 03:29 AM)sweetysuckscock Wrote: Got one solution add a reference to Windows.forms and
CodeSystem.Windows.Forms.Application.Run()
You're welcome :)
Application.Run(); is essentially (in this situation) equal to my previous code, it sets up a loop that checks for windows messages (purely anecdotal, this is just what I recall from my memory) and calls events.
* - CodeAssassin - May 27, 2015
(May 27, 2015 03:43 AM)AlphaDelta Wrote: Choke the main thread, something like
should do just fine, the CPU usage is virtually non-existent.PHP Code
<?php
while(running) Thread.Sleep(100);
Application.Run(); is essentially (in this situation) equal to my previous code, it sets up a loop that checks for windows messages (purely anecdotal, this is just what I recall from my memory) and calls events.
Under the hood application run is a winapi function hooked into the message loop of the application, not quite a while loop more low lever then a normal while loop, So i expect it to preform a LOT better then while (true) thead.sleep
Code of message loop Application.Run() is hooked into
Code
int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE, LPSTR lpCmdLine, int nCmdShow)
{
MSG msg;
BOOL bRet;
while((bRet = GetMessage(&msg, NULL, 0, 0)) != 0)
{
if(bRet == -1)
{
// Handle Error
}
else
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
}
return msg.wParam;
}From what i read the optimal way is to make the task a windows service and just have it run the tasks that need performing, could be an option.
* - d3agle - May 27, 2015
(May 27, 2015 03:06 AM)BahNahNah Wrote: Wouldn't that also use high resources?
There must be a better way of doing it, how do rat stubs stay open?
Take a look here to see how xRAT stays open.
https://github.com/MaxXor/xRAT/blob/master/Client/Program.cs