Forums Feature Suggestions raw sockets

implement raw sockets in mIRC

Why?

I can't see what purpose this could fulfil other than allowing drones to synflood and send xmas-tree packets without the need for a .dll or seperate .exe in their payload.

Even then, isn't this limited by the users operating system?

not that it's any where near a good enough reason to implement them, but it would give you more privacy when using sockets.
and yes it's limited to windows XP.

edit: obviously they can be used for that sort of thing, but i highly doubt anyone would use mIRC for flooding when there are many other (faster) packet bots out there.

*hollow laugh*

Consider how many mIRC-based spam/pr0n/infected-website-advertising drones there are ALREADY on IRC - I bet the kiddies would just love to add the extra 'feature'.

Besides which, the flooding could be built into scripts and more easily downloaded/used by the innocent/naive.

PM

Tidy is correct though. Despite the number of trojans that use mIRC has its host, the smarter "packet kiddies" would stick to a c\c++ exe or dll to do their dirty work. Considering count and speed, almost anything external to mIRC is faster.

But just on a side note, most ISP are resricting "spoofed" packet headers anyways. So in essence, the use of a raw socket will be almost obsolete external to your own network.

sure they use mIRC for that, but that's because mIRC does the job well.
but as kt said.. a c/c++ one is more likely to be used.

hrm... wud it be easy to make a trojan or summit in mirc if they introduced raw sockets....?
coz if it wud be, seems mirc is sutch a small aplication as to c+ or summit. you would find that all the people that just want to learn hackin n [censored] will download mirc instead of doloading more that 100 mb...
agree?

nobody would use mirc to write a trojan for syn flooding when c++ is a lot faster and you can't see whats in the source code.
with mIRC you can check/get someone to check what the script does before running it.

very good point. my bad

and tidy trax.... just following on to your point if they did actualy open a trojan via mirc. they cud easly just look at the code and fix it.

You are right about the numbers out there. While I disagree that mIRC would be a worthy packet tool on its own (it wouldnt loop fast enough), if you had several clients at your command, and many people undoubtably do, you can probably send all the packets you would want to from any 1 ip anyway without any significant slowdown in a victim's mIRC client. In fact, I have already seen UDP flood scripts for such distributed attacks, but I have no idea if they actually work.

they do work, but they don't have ip spoofing, the only thing raw sockets would allow that can't already be done is ip spoofing.

i belive that can be very good for my proxy, making it tranparent