UDP API DEV: Difference between revisions

UDP API DEV (view source)

Revision as of 05:27, 27 January 2006

569 bytes added , 27 January 2006

m

→‎ENCRYPT

Exp

Bureaucrats, Administrators

340

edits

@@ Line 82: / Line 82: @@
 == Misc Commands ==
 === ENCRYPT ===
-Will cause all responses, except the first, to be encrypted (128 bit AES). The client will also have to encrypt the requests. The encryption key is the md5 hash of a special (new/to be added) password defined in the users profile. Normal AUTH is still necessary to authenticate.
+Will cause all future messages from the server, except the first (the reply to the ENCRYPT command itself), to be encrypted (128 bit 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 MD5 hash of a special (new/to be added) password defined in the users profile. A normal AUTH message is still necessary to authenticate and should follow the ENCRYPT command once the API has acknowledged the encryption.
 '''Command String:'''
@@ Line 96: / Line 96: @@
 * user is username
 * type is type of encryption, 1 => 128 bit AES, none other defined atm
-* encryption pass must be set in profile settings
+* encryption pass must be set in profile settings on the website
-* not possible to disable/escape.
+* it is not possible to disable the encryption once enabled while staying logged in
+* a logout (the logout message needs to be correctly encrypted) or timeout will disable the encryption
+* in order to minimize server load, encryption should be disabled by default and should have to be enabled manually by the user in the configuration options.
 [[Category:Development]]