Luigi Auriemma

I cant seem to get it to work i even compiled it and this is exactly what i do.

1.) CD C:\Exploit (where sudpipe is along with the .dll)
2.) sudppipe -l myproxocket.dll ********* 27015 27015
3.) go into garrysmod and type "Connect 127.0.0.1:27015" yet it doesnt connect to anything even though you tell us to connect the client to it :< any help?

This is the source + dll of the prog

http://www.mediafire.com/?ndyywdcnmwt

it's enough useless that you upload "source+dll" since I'm the author ot them and its absolutely not needed to recompile myproxocket.dll for verifying the 2 vulnerabilities of that advisory (hex editor job).

while about the problem the only thing you can do is checking in the window of sudppipe if is displayed the message:
which means that the connection from the client has been successfully received and so can be excluded an error in it (that in any case is not caused by sudppipe).

actully i figured out that you cant use 127.0.0.1 on my computer, i have to use my actuall lan ip EX 192.168.2.XX
but the plugin still wont upload the test.txt to the other pc, i put the default file in the .C file to

"C:\test.txt"
then i check my host yet the file doesnt upload there :<

that proof-of-concept doesn't perform the upload of a real file, it simply creates an empty file in the arbitrary location provided where is located the XXXXXXXXX...XXX string into the remote server to test.
while there are no limitations for the file deletion testing.

Oh so i cant actully upload any real files with data inside of them? O_o

exactly, you can only create them

another question, how would i go about having multiple ports but the same ip? for sudppipe?

uhmmm I guess to have understood your question (something like sending the same packets to SERVER:1234 SERVER:1235 SERVER:1236 and so on) but this is not possible in the Source engine and practically in almost all the other games due to the handshakes/challenges and other details of the protocol (ids, qports and so on).

anyway sudppipe implements 2 options for doing a similar job:
-X the packets will be sent to all the specified hosts using a new local port
-Y the packets will be sent to all the specified hosts using the same local port

example:
I have used 0 as destination port because all the hosts I have specified have their port (:port)

No, thats not what i want :D. i want like.

1.2.3.4:27015,1.2.3.5:27015,1.2.3.6:27015 0 1234 would that work?

sudppipe can do anything but remains the problem that the Source servers will never accept the connections for that technical feature of the protocol I told in the previous post