[Proxy] Corrupt input stream on connection?

Code:

Waiting for client connection...
Waiting for client connection...
Next address: 184.169.130.44
Client connected (1): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (1): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (2): 127.0.0.1
Corrupted stream? packetLength = 1014001516
Waiting for client connection...
Next address: 184.169.130.44
Client connected (3): 127.0.0.1
Corrupted stream? packetLength = 1014001516
Waiting for client connection...
Next address: 184.169.130.44
Corrupted stream? packetLength = 1014001516
Client connected (4): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (5): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (6): 127.0.0.1
Corrupted stream? packetLength = 1014001516
Waiting for client connection...
Next address: 184.169.130.44
Client connected (7): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (8): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (9): 127.0.0.1
Attempt reset of connection. (19 bytes skipped)
Attempt reset of connection. (19 bytes skipped)
Attempt reset of connection. (19 bytes skipped)
Attempt reset of connection. (19 bytes skipped)
Waiting for client connection...
Next address: 184.169.130.44
Client connected (6): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (7): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (8): 127.0.0.1
Waiting for client connection...
Next address: 184.169.130.44
Client connected (9): 127.0.0.1

That is the output I got from my proxy when connecting 9 clients at once. For some reason the client sends a packet reporting a length of 1014001516 with an id of 105 if I remember correctly (btw not a valid packet id). This was the cause of the outofmemory error I spoke of in my other thread. For now I made a condition to check the packet length and if it's of bogus length skip it. Anyone know why this happens? I remember someone talking about this issue, might of been @flyrocket, just trying to understand why it happens and what can be done to fix it.

@ @nilly Yes, @flyrocket had the same problem when creating OryxDom, so I'm assuming that you're using Ikulip's source? In that case, Ill have to advice you to migrate to fury's source.

Originally Posted by UltraN00b

@ @nilly Yes, @flyrocket had the same problem when creating OryxDom, so I'm assuming that you're using Ikulip's source? In that case, Ill have to advice you to migrate to fury's source.

Well I'm not migrating to fury's. At least not anytime soon. I just rewrote the proxy portion (keeping the base the same) to use a thread safe queuing structure. The proxy functions just fine, other than that small annoyance I wrote about above. I just wanted to get some information on it.

Check thou PM.

Originally Posted by UltraN00b

@ @nilly Yes, @flyrocket had the same problem when creating OryxDom, so I'm assuming that you're using Ikulip's source? In that case, Ill have to advice you to migrate to fury's source.

Yup, furyhunter's one works fine.
@UltraN00b And did you know what was the problem? I feel it could be related to RC4 deciphering because i see no reason why the client would send us such a bad packet. But its just a supposition.

Well it isn't related to RC4 because the packet length and id isn't encrypted. The length of the packet is the first thing you get, then the id, after that is the data (which is the encrypted rc4 stuff).

This is the exact problem that had me pulling my hair out in frustration when running my server. Basically, print the bytes as chars and see what you get. Also: port 843.

@ @JustAnoobROTMG I don't know, but what I do know, is that @flyrocket avoided this mess by rewriting OryxDom using Fury's API.

Originally Posted by marinepower

This is the exact problem that had me pulling my hair out in frustration when running my server. Basically, print the bytes as chars and see what you get. Also: port 843.

Thanks for this. This is the answer I was looking for. It turns out it is a string -> "<policy-file-request/>". From what little reading I've done, I guess this is a message sent out by the flash player for each new connection? I'll have to read up on this policy file a bit more to understand it and what it does.

I think I am out of topic ...
but last time my proxy failled , crashing at startup with strange length

pe ... well it was coming from an unexpected program that installed and listening on this port, it was "my-config", lol... took me time to figure it out

sorry I am off topic but this was funny

@ @nilly Ah the Crossdomain Policy! @marinepower you're a god! I would've never figured it out. UTF-8 Encoded? Or ASCII?

Originally Posted by UltraN00b

@ @nilly Ah the Crossdomain Policy! @marinepower you're a god! I would've never figured it out. UTF-8 Encoded? Or ASCII?

I'm guessing ascii? Is there a way to tell the difference between the two if the only characters you get is standard ascii?

---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------

BTW I replaced the policy server class from ikulip's source to the one contained in fury's. Seemed to have fixed the program.

[Proxy] Corrupt input stream on connection?

Post a Reply

Similar Threads

Tags for this Thread