You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
I want to ask about encrypting packets, I have some problem with that.
When we encrypt packet headers (send from client), we encrypt 6 bytes (as an example: CMSG_CHAR_CREATE), Since we are using a Circular buffer the next offset will be 6 bytes (and so on each time +6 bytes on the next send from the client, offset 6,12,18,24...). This works fine for me and the server understands and correctly decodes the packet headers. But the problem comes when I (the client) try to decode the response (server) headers. We must always decode exactly 4 bytes of the server header (as always, shouldn't we? as an example SMSG_CHAR_CREATE). I can only decrypt the header of the first packet. Further, all other packets coming from the server cannot be decrypted by me. Here we use the same Circular buffer, only offset is now +4 bytes (4,8,12,16...) - SMSG (server) headers are always 4 bytes
Hi!
I want to ask about encrypting packets, I have some problem with that.
When we encrypt packet headers (send from client), we encrypt 6 bytes (as an example: CMSG_CHAR_CREATE), Since we are using a Circular buffer the next offset will be 6 bytes (and so on each time +6 bytes on the next send from the client, offset 6,12,18,24...). This works fine for me and the server understands and correctly decodes the packet headers. But the problem comes when I (the client) try to decode the response (server) headers. We must always decode exactly 4 bytes of the server header (as always, shouldn't we? as an example SMSG_CHAR_CREATE). I can only decrypt the header of the first packet. Further, all other packets coming from the server cannot be decrypted by me. Here we use the same Circular buffer, only offset is now +4 bytes (4,8,12,16...) - SMSG (server) headers are always 4 bytes
Am I making a mistake somewhere?
BotFarm/Client/Crypto/ARC4.cs
Lines 47 to 64 in 6ee6f47
The text was updated successfully, but these errors were encountered: