moparisthebest/rswiki-book
1
0
Fork 0
mirror of https://github.com/moparisthebest/rswiki-book synced 2024-11-25 10:32:17 -05:00
Code Issues Releases Wiki Activity

Update MediaWiki page '317 Protocol'

Browse Source
This commit is contained in:
t4 2011-06-18 16:52:55 +00:00 committed by moparisthebest
parent ae7209b3cf
commit ec897a9b5c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
317-Protocol.mediawiki
View File

@ -1,7 +1,7 @@
[[Category Packet]] [[Category Packet]]
[[Category Packet 317]] [[Category Packet 317]]
{{Crappy}} {{Crappy}}
<P ALIGN="RIGHT"><img src="http://img542.imageshack.us/img542/6853/ak1.jpg" alt="317" /></P> <P ALIGN="RIGHT">[[File 317_1.jpg]]</P>
== '''Packet structure''' == == '''Packet structure''' ==
When the client sends a packet to the server, the first byte encapsulates its opcode. This specific opcode is encrypted with a value generated by the ISAAC PRNG seeded with a dynamically server generated key during the login block. The server decrypts it and associates the opcode to the packet's respective predefined size. If the packet does not contain a fixed size, the opcode will be followed by either a byte or a word - varying per packet - for its proper size. This is then followed by the payload. When the client sends a packet to the server, the first byte encapsulates its opcode. This specific opcode is encrypted with a value generated by the ISAAC PRNG seeded with a dynamically server generated key during the login block. The server decrypts it and associates the opcode to the packet's respective predefined size. If the packet does not contain a fixed size, the opcode will be followed by either a byte or a word - varying per packet - for its proper size. This is then followed by the payload.