Socket.ssl - Revision history

Dana at 15:26, 21 January 2013

2013-01-21T15:26:20Z

Dana at 15:21, 14 November 2012

2012-11-14T15:21:40Z

Dana at 15:19, 14 November 2012

2012-11-14T15:19:46Z

Dana at 15:18, 14 November 2012

2012-11-14T15:18:13Z

Dana at 15:14, 14 November 2012

2012-11-14T15:14:53Z

Dana: Created page with " The socket.ssl message is sent by a module requesting to turn a regular TCP socket into a SSL/TLS encrypted one. Parameters ;server : Boolean value requesting to negotia..."

2012-11-14T15:13:16Z

Created page with " The socket.ssl message is sent by a module requesting to turn a regular TCP socket into a SSL/TLS encrypted one. Parameters ;server : Boolean value requesting to negotia..."

New page

The socket.ssl message is sent by a module requesting to turn a regular TCP socket into a SSL/TLS encrypted one.

Parameters

;server
: Boolean value requesting to negotiate SSL as server. Defaults to false if missing (negotiate as client)
;verify
: Keyword describing if and when the remote certificate is to be verified

:* none - Don't ask for a certificate, don't stop if verification fails (default)
:* peer - Certificate is verified only if provided (a server always provides one)
:* only - Server only - verify client certificate only if provided and only once
:* must - Server only - client must provide a certificate at every (re)negotiation
:* once - Server only - client must provide a certificate only at first negotiation

;context
: Name of the SSL server context to use to secure the connection, if set overrides the domain parameter
;domain
: The domain used ti identify the SSL server context, used only if context isn't set explicitely
;test
: Boolean value requesting a test only (no socket replace). Defaults to false if missing

'''NOTE:''' The message's user data object must be able to return a "Socket*" object. This must point to a pointer to the Socket object to modify. On a successful return the original Socket object is destroyed and replaced with a derived object with SSL capabilities. The pointer to the new object is placed into the provided pointer.

← Older revision		Revision as of 15:26, 21 January 2013
Line 23:		Line 23:

	'''NOTE:''' The message's user data object must be able to return a "Socket*" object. This must point to a pointer to the Socket object to modify. On a successful return the original Socket object is destroyed and replaced with a derived object with SSL capabilities. The pointer to the new object is placed into the provided pointer.		'''NOTE:''' The message's user data object must be able to return a "Socket*" object. This must point to a pointer to the Socket object to modify. On a successful return the original Socket object is destroyed and replaced with a derived object with SSL capabilities. The pointer to the new object is placed into the provided pointer.
		+
		+
		+	'''See also'''
		+
		+	*[[socket.sctp]]

@@ Line 2: / Line 2: @@
 The '''socket.ssl''' message is sent by a module requesting to turn a regular TCP socket into a SSL/TLS encrypted one.
-Parameters
+===Parameters===
 ;server

← Older revision		Revision as of 15:19, 14 November 2012
Line 1:		Line 1:

−	The socket.ssl message is sent by a module requesting to turn a regular TCP socket into a SSL/TLS encrypted one.	+	The '''socket.ssl''' message is sent by a module requesting to turn a regular TCP socket into a SSL/TLS encrypted one.

	Parameters		Parameters

@@ Line 18: / Line 18: @@
 :    Name of the SSL server context to use to secure the connection, if set overrides the domain parameter
 ;domain
-:    The domain used ti identify the SSL server context, used only if context isn't set explicitely
+:    The domain used ti identify the SSL server context, used only if context isn't set explicitly
 ;test
 :    Boolean value requesting a test only (no socket replace). Defaults to false if missing
 '''NOTE:''' The message's user data object must be able to return a "Socket*" object. This must point to a pointer to the Socket object to modify. On a successful return the original Socket object is destroyed and replaced with a derived object with SSL capabilities. The pointer to the new object is placed into the provided pointer.

@@ Line 9: / Line 9: @@
 :    Keyword describing if and when the remote certificate is to be verified
-:*        none - Don't ask for a certificate, don't stop if verification fails (default)
+:* none - Don't ask for a certificate, don't stop if verification fails (default)
-:*        peer - Certificate is verified only if provided (a server always provides one)
+:* peer - Certificate is verified only if provided (a server always provides one)
-:*        only - Server only - verify client certificate only if provided and only once
+:* only - Server only - verify client certificate only if provided and only once
-:*        must - Server only - client must provide a certificate at every (re)negotiation
+:* must - Server only - client must provide a certificate at every (re)negotiation
-:*        once - Server only - client must provide a certificate only at first negotiation
+:* once - Server only - client must provide a certificate only at first negotiation
 ;context