BZAuthd - Revision history

JeffM2501: Fix categories

2013-02-09T23:31:23Z

Fix categories

← Older revision		Revision as of 23:31, 9 February 2013
Line 202:		Line 202:
	** LDAP (likely if possible)		** LDAP (likely if possible)
	** KARMA (unlikely – doesn't seem to make logical sense)		** KARMA (unlikely – doesn't seem to make logical sense)

	~~[[Category:TODO]]~~

JeffM2501: not a stub

2013-02-09T23:30:45Z

not a stub

← Older revision		Revision as of 23:30, 9 February 2013
Line 203:		Line 203:
	** KARMA (unlikely – doesn't seem to make logical sense)		** KARMA (unlikely – doesn't seem to make logical sense)

	~~{{stub}}~~
	[[Category:TODO]]		[[Category:TODO]]

Wyk3d: /* Network Protocol */

2008-07-04T16:37:33Z

Network Protocol

← Older revision		Revision as of 16:37, 4 July 2008
Line 134:		Line 134:
	denote whether they originated from a server a client or a daemon, or just MSG if it may originate from either of these. For inter-node communication, the additional prefixes might be used.		denote whether they originated from a server a client or a daemon, or just MSG if it may originate from either of these. For inter-node communication, the additional prefixes might be used.

	MSG_HANDSHAKE - first packet sent by both parties when opening any communication - Contains: 2 byte type id (0 - client/1 - server/2 - daemon) 2 byte protocol version number, x bytes of additional information based on the type and protocol version (e.g client version, daemon rank, etc)		MSG_HANDSHAKE - first packet sent by both parties when opening any communication - Contains: 1 byte type id (0 - client/1 - server/2 - daemon) 2 byte protocol version number, x bytes of additional information based on the type and protocol version (e.g client version, daemon rank, etc)

	Protocol version 1:		Protocol version 1:

Wyk3d: /* Network Protocol */

2008-06-30T13:59:14Z

Network Protocol

← Older revision		Revision as of 13:59, 30 June 2008
Line 138:		Line 138:
	Protocol version 1:		Protocol version 1:

	CMSG_HANDSHAKE - the client specific version of the handshake - Contains: the data from MSG_HANDSHAKE followed by a 4 byte integer for the client version and a 2 byte integer for the type of communication requested (can be 0 - auth, 1 - register get form, 2 - register request) - Note: the client may request other communication types without closing the connection later on		CMSG_HANDSHAKE - the client specific version of the handshake - Contains: the data from MSG_HANDSHAKE followed by a 4 byte integer for the client version and a 2 byte integer for the type of initial communication requested (can be 0 - auth, 1 - register get form, 2 - register request) - Note: the client may request other communication types without closing the connection later on

	DMSG_HANDSHAKE - the daemon specific version of the handshake - Contains: the data from MSG_HANDSHAKE followed by a 4 byte integer containing the daemon version and a 2 byte integer denoting the daemon rank		DMSG_HANDSHAKE - the daemon specific version of the handshake - Contains: the data from MSG_HANDSHAKE followed by a 4 byte integer containing the daemon version and a 2 byte integer denoting the daemon rank
Line 168:		Line 168:

	DMSG_REGISTER_SUCCESS - sent if the registration was successful - Contains: nothing		DMSG_REGISTER_SUCCESS - sent if the registration was successful - Contains: nothing

			SMSG_TOKEN_VALIDATE - sent when the server wishes to validate tokens that it got from a client - Contains: a 1 byte integer "n" for the number of tokens to be validated followed by "n" 4 byte integer tokens

			DMSG_TOKEN_VALIDATE - sent when the daemon processed a validation request - Contains: a 1 byte integer "n" for the number of tokens to be validated followed by "n" 4 byte integer error codes which are 0 where the the token was successfully validated

	= Use Cases =		= Use Cases =

Wyk3d: /* Network Protocol */

2008-06-30T13:41:58Z

Network Protocol

← Older revision		Revision as of 13:41, 30 June 2008
Line 138:		Line 138:
	Protocol version 1:		Protocol version 1:

	~~CMSG_AUTH_REQUEST~~ - ~~sent before~~ a client ~~connects to~~ a ~~server~~ - ~~Contains~~: ~~C string username~~		CMSG_HANDSHAKE - the client specific version of the handshake - Contains: the data from MSG_HANDSHAKE followed by a 4 byte integer for the client version and a 2 byte integer for the type of communication requested (can be 0 - auth, 1 - register get form, 2 - register request) - Note: the client may request other communication types without closing the connection later on

	~~DMSG_AUTH_REQUEST_DENIED~~ - ~~sent after an auth request if it was denied~~ - Contains: a 4 byte ~~error code~~		DMSG_HANDSHAKE - the daemon specific version of the handshake - Contains: the data from MSG_HANDSHAKE followed by a 4 byte integer containing the daemon version and a 2 byte integer denoting the daemon rank

	~~DMSG_AUTH_REQUEST_ACCEPTED~~ - ~~sent after an auth request if it was accepted~~ - Contains: ~~a binary string containing~~ the ~~public key "n" value and~~ a 2 byte integer ~~containing~~ the ~~public key "e" value~~		SMSG_HANDSHAKE - the server specific version of the handshake - Contains: the data from MSG_HANDSHAKE followed by a 4 byte integer for the server version

	~~CMSG_AUTH_CIPHER~~ - sent if the auth ~~request~~ was ~~accepted~~ - Contains: ~~binary string for the cipher of the password~~		CMSG_AUTH_REQUEST - this may be sent to notify the daemon that an auth is requested, but is not needed if this was already specified in the handshake - Contains: nothing

	DMSG_AUTH_FAIL - sent if the auth failed - Contains: 4 byte error code		DMSG_AUTH_FAIL - sent after the auth request or response, if the auth failed for some reason (e.g unknown user name, incorrect password etc) - Contains: a 4 byte error code, perhaps followed by a C string with more information

			DMSG_AUTH_CHALLENGE - sent after an auth request if it was accepted - Contains: a binary string containing the public key "n" value and a 2 byte integer containing the public key "e" value

			CMSG_AUTH_RESPONSE - sent if the auth request was accepted, after the public key was received - Contains: binary string for an encrypted message containing the username and the password delimited by a space

	DMSG_AUTH_SUCCESS - sent if the auth succeeded - Contains: 4 byte integer session token to be sent to a server		DMSG_AUTH_SUCCESS - sent if the auth succeeded - Contains: 4 byte integer session token to be sent to a server

	CMSG_REGISTER_GET_FORM - sent when the user tries to access the register menu - Contains: nothing		CMSG_REGISTER_GET_FORM - sent when the user tries to access the register menu, but is not needed if this was already specified in the handshake - Contains: nothing

			DMSG_REGISTER_FAIL - sent whenever if getting the form failed or if the request was denied or if the challenge failed etc - Contains: a 4 byte error code, perhaps followed by a C string with more information

	DMSG_REGISTER_SEND_FORM - sent after a form request - Contains: C String that describes the fields that the user is asked to complete		DMSG_REGISTER_SEND_FORM - sent after a form request - Contains: C String that describes the fields that the user is asked to complete

	CMSG_REGISTER_REQUEST - sent when the user completed the form - Contains: nothing		CMSG_REGISTER_REQUEST - sent when the user completed the form, but is not needed if this was already specified in the handshake - Contains: nothing

			DMSG_REGISTER_CHALLENGE - sent if the provided preliminary information is valid - Contains: a binary string containing the public key "n" value and a 2 byte integer containing the public key "e" value

			CMSG_REGISTER_RESPONSE - sent if the register request was accepted and a key was received - Contains:
			a binary string for an encrypted message contain the username, the password and other information, each delimited by a space

			DMSG_REGISTER_SUCCESS - sent if the registration was successful - Contains: nothing

	= Use Cases =		= Use Cases =

Wyk3d: /* Network Protocol */

2008-06-29T23:45:11Z

Network Protocol

← Older revision		Revision as of 23:45, 29 June 2008
Line 129:		Line 129:
	- binary strings, preceded by a 2 byte length descriptor		- binary strings, preceded by a 2 byte length descriptor

	~~Packet structure~~ and ~~descriptions~~:		Opcode descriptions and data contents:

	The opcodes will be denoted by constants, they will be prefixed with either CMSG, SMSG or DMSG to		The opcodes will be denoted by constants, they will be prefixed with either CMSG, SMSG or DMSG to

Wyk3d: /* Network Protocol */

2008-06-29T23:44:03Z

Network Protocol

← Older revision		Revision as of 23:44, 29 June 2008
Line 149:		Line 149:

	DMSG_AUTH_SUCCESS - sent if the auth succeeded - Contains: 4 byte integer session token to be sent to a server		DMSG_AUTH_SUCCESS - sent if the auth succeeded - Contains: 4 byte integer session token to be sent to a server

			CMSG_REGISTER_GET_FORM - sent when the user tries to access the register menu - Contains: nothing

			DMSG_REGISTER_SEND_FORM - sent after a form request - Contains: C String that describes the fields that the user is asked to complete

			CMSG_REGISTER_REQUEST - sent when the user completed the form - Contains: nothing

	= Use Cases =		= Use Cases =

Wyk3d: /* Network Protocol */

2008-06-29T23:22:10Z

Network Protocol

← Older revision		Revision as of 23:22, 29 June 2008
Line 139:		Line 139:

	CMSG_AUTH_REQUEST - sent before a client connects to a server - Contains: C string username		CMSG_AUTH_REQUEST - sent before a client connects to a server - Contains: C string username

	DMSG_AUTH_REQUEST_DENIED - sent after an auth request if it was denied - Contains: a 4 byte error code		DMSG_AUTH_REQUEST_DENIED - sent after an auth request if it was denied - Contains: a 4 byte error code

	DMSG_AUTH_REQUEST_ACCEPTED - sent after an auth request if it was accepted - Contains: a binary string containing the public key "n" value and a 2 byte integer containing the public key "e" value		DMSG_AUTH_REQUEST_ACCEPTED - sent after an auth request if it was accepted - Contains: a binary string containing the public key "n" value and a 2 byte integer containing the public key "e" value

	CMSG_AUTH_CIPHER - sent if the auth request was accepted - Contains: binary string for the cipher of the password		CMSG_AUTH_CIPHER - sent if the auth request was accepted - Contains: binary string for the cipher of the password

	DMSG_AUTH_FAIL - sent if the auth failed - Contains: 4 byte error code		DMSG_AUTH_FAIL - sent if the auth failed - Contains: 4 byte error code

	DMSG_AUTH_SUCCESS - sent if the auth succeeded - Contains: 4 byte integer session token to be sent to a server		DMSG_AUTH_SUCCESS - sent if the auth succeeded - Contains: 4 byte integer session token to be sent to a server

Wyk3d: /* Network Protocol */

2008-06-29T23:20:52Z

Network Protocol

@@ Line 122: / Line 122: @@
 - integer types of 1,2,4 or 8 bytes in size, sent in binary, little-endian, with no delimiter
 - C strings, with a 0 delimiter at the end
 - binary strings, preceded by a 2 byte length descriptor
 = Use Cases =

Wyk3d: /* Network Protocol */

2008-06-29T22:20:13Z

Network Protocol

← Older revision		Revision as of 22:20, 29 June 2008
Line 114:		Line 114:

	The packet format for all communication between client/server/daemons will be as follows:		The packet format for all communication between client/server/daemons will be as follows:

	- 4 byte packet header containing: a 2 byte opcode followed by the 2 byte data length		- 4 byte packet header containing: a 2 byte opcode followed by the 2 byte data length

	- the rest of the data, between 0 and a theoretical maximum of 65k bytes, but capped at 4096 bytes, this can be increased later if larger packets are needed		- the rest of the data, between 0 and a theoretical maximum of 65k bytes, but capped at 4096 bytes, this can be increased later if larger packets are needed

	The information in the data field will be structured into:		The information in the data field will be structured into:

	- integer types of 1,2,4 or 8 bytes in size, sent in binary, little-endian, with no delimiter		- integer types of 1,2,4 or 8 bytes in size, sent in binary, little-endian, with no delimiter

	- C strings, with a 0 delimiter at the end		- C strings, with a 0 delimiter at the end

	- binary strings, preceded by a 2 byte length descriptor		- binary strings, preceded by a 2 byte length descriptor