luckyone-cc / shredder

Layer 4 DoS Tool in C#

Hello 👀, I'm Tom!

A passionate C# developer who enjoys building innovative and exceptional software solutions

- To be honest with you. Most of my projects are closed source. Sorry about that. -

Technologies used:

Version Control and Development tools used:

Operating Systems familiar with:

 

 

 

• Discord: the.luckyone

shredder's Issues

Calling Shred#Info twice

Shredder/Shred.cs

Line 39 in 4dc09b1

await Task.Run(Info);

Shredder/Program.cs

Line 58 in 4dc09b1

Task infoTask = Task.Run(() => shred.Info());

See title. I dont think it should do that?

UpdClient#SendAsync cannot be multithreaded; Making the threads parameter useless

The following lines and code paths are affected:

Shredder/Program.cs

Line 53 in 72579f8

int threads = string.IsNullOrWhiteSpace(threadsInput) ? 100 : 0;

Shredder/Program.cs

Line 67 in 72579f8

Shred shred = new Shred(ip, port, force, threads);

Shredder/Shred.cs

Lines 39 to 42 in 72579f8

	for (int i = 0; i < _threads; i++)
	{
	await Task.Run(SendAsync);
	}

---

When replacing the "100" with only "1" you will notice that both 100 threads and 1 thread yield the same throughput.

---

That's because Sockets do not allow concurrent SendAsync() calls.

See
dotnet/runtime#26843 (comment)
https://tangentsoft.com/wskfaq/intermediate.html#threadsafety

3.10 - Is Winsock thread-safe?
On modern Windows stacks, yes, it is, within limits.
It is safe, for instance, to have one thread calling send() and another thread calling recv() on a single socket.
By contrast, it’s a bad idea for two threads to both be calling send() on a single socket. This is “thread-safe” in the limited sense that your program shouldn’t crash, and you certainly shouldn’t be able to crash the kernel, which is handling these send() calls. The fact that it is “safe” doesn’t answer key questions about the actual effect of doing this. Which call’s data goes out first on the connection? Does it get interleaved somehow? Don’t do this.
Instead of multiple threads accessing asingle socket, you may want to consider setting up a pair of network I/O queues.

Test