staff
2,096
edits
UDP API Definition: Difference between revisions
→Authing Commands
No edit summary |
|||
| Line 211: | Line 211: | ||
**The server will compress (instead of truncating) the datagrams when needed if this option is enabled. | **The server will compress (instead of truncating) the datagrams when needed if this option is enabled. | ||
**The first two bytes of compressed datagrams will always be set to zero. (So tags should never start with that.) | **The first two bytes of compressed datagrams will always be set to zero. (So tags should never start with that.) | ||
* Default [ | * Default [[Wikipedia:MTU (networking)|''MTU'']] is 1400. Minimum allowed is 400, maximum 1400, due [[Wikipedia:Point-to-Point Protocol over Ethernet|PPPoE]]. | ||
---- | ---- | ||
| Line 228: | Line 228: | ||
---- | ---- | ||
=== ENCRYPT: Start Encrypted Session === | === ENCRYPT: Start Encrypted Session === | ||
Will cause all future messages from the server, except the first (the reply to the ENCRYPT command itself), to be encrypted (128 bit [ | Will cause all future messages from the server, except the first (the reply to the ENCRYPT command itself), to be encrypted (128 bit [[Wikipedia:Advanced Encryption Standard|AES]]). The client will also have to encrypt all future requests sent to the server. All non-encrypted messages will be discarded by the server. The encryption key is the [[Wikipedia:MD5|MD5]] hash of a special ''API Password'' (defined in the users profile) concatenated with the salt string as given in the reply to the ENCRYPT message. A normal AUTH message is still necessary to authenticate and should follow the ENCRYPT command once the API has acknowledged the encryption. | ||
'''Command String:''' | '''Command String:''' | ||