JANUS SSLSTAT or SSLSTATUS - Revision history

JAL: link repair

2016-05-31T22:47:06Z

link repair

← Older revision		Revision as of 22:47, 31 May 2016
Line 2:		Line 2:
	<span class="pageSubtitle">Display SSL activity</span>		<span class="pageSubtitle">Display SSL activity</span>

	<var>JANUS SSLSTAT</var> and <var>JANUS SSLSTATUS</var> are simply two ways of issuing the same command. The <var>JANUS SSLSTAT</var> or <var>SSLSTATUS</var> command provides a detailed display of the SSL activity for each combination of Janus port and network security protocol. "SSL activity" refers to <var class="product">[[~~Media:jansslrNew.pdf\|~~Janus Network Security]]</var> encrypted communications on a Janus port whose definition includes an SSL parameter specification. <var class="product">Janus Network Security</var> supports the SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols.		<var>JANUS SSLSTAT</var> and <var>JANUS SSLSTATUS</var> are simply two ways of issuing the same command. The <var>JANUS SSLSTAT</var> or <var>SSLSTATUS</var> command provides a detailed display of the SSL activity for each combination of Janus port and network security protocol. "SSL activity" refers to <var class="product">[[Janus Network Security]]</var> encrypted communications on a Janus port whose definition includes an SSL parameter specification. <var class="product">Janus Network Security</var> supports the SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols.

	==Syntax==		==Syntax==

JAL: misc cleanup

2015-09-23T15:30:47Z

misc cleanup

← Older revision		Revision as of 15:30, 23 September 2015
Line 2:		Line 2:
	<span class="pageSubtitle">Display SSL activity</span>		<span class="pageSubtitle">Display SSL activity</span>

	JANUS SSLSTAT and JANUS SSLSTATUS are simply two ways of issuing the same command. The JANUS SSLSTAT or SSLSTATUS command provides a detailed display of the SSL activity for each combination of Janus port and network security protocol. "SSL activity" refers to ''[~~http~~:~~//www.sirius-software.com/maint/download/jansslr~~.pdf Janus Network Security]'' encrypted communications on a Janus port whose definition includes an SSL parameter specification. <var class="product">Janus Network Security</var> supports the SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols.		<var>JANUS SSLSTAT</var> and <var>JANUS SSLSTATUS</var> are simply two ways of issuing the same command. The <var>JANUS SSLSTAT</var> or <var>SSLSTATUS</var> command provides a detailed display of the SSL activity for each combination of Janus port and network security protocol. "SSL activity" refers to <var class="product">[[Media:jansslrNew.pdf\|Janus Network Security]]</var> encrypted communications on a Janus port whose definition includes an SSL parameter specification. <var class="product">Janus Network Security</var> supports the SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols.

	==Syntax==		==Syntax==
	<p class="syntax">JANUS SSLSTATUS portname		<p class="syntax">JANUS SSLSTATUS <span class="term">portname</span>
	</p>		</p>

Line 13:		Line 13:
	<p class="code">JANUS SSLSTATUS *</p>		<p class="code">JANUS SSLSTATUS *</p>

	<p class="~~code~~"> Name Port Type Stat Prot Connects SesNew SesNF SesTO Errs		<p class="output"> Name Port Type Stat Prot Connects SesNew SesNF SesTO Errs
	JANWEBS 443 WEBSERV Start SSLV2 1 1 0 0 0		JANWEBS 443 WEBSERV Start SSLV2 1 1 0 0 0
	JANWEBS 443 WEBSERV Start 3/TLS 308 180 0 0 30		JANWEBS 443 WEBSERV Start 3/TLS 308 180 0 0 30
Line 28:		Line 28:
	</p>		</p>

	==~~Output~~==		==Command output==
	<var>JANUS SSLSTATUS</var> provides the following information:		<var>JANUS SSLSTATUS</var> provides the following columns of information:
	<table>		<table>
	<tr><th><var>Name</var></th>		<tr><th><var>Name</var></th>
Line 51:		Line 51:
	<td>Number of TCP/IP connections made to the port.		<td>Number of TCP/IP connections made to the port.
	<p>		<p>
	For a WEBSERV port, this corresponds to the number of "hits" or pages requested from the server.</p></td></tr>		For a <var>[[JANUS DEFINE#type\|WEBSERV]]</var> port, this corresponds to the number of "hits" or pages requested from the server.</p></td></tr>

	<tr><th><var>SesNew</var></th>		<tr><th><var>SesNew</var></th>

JAL: /* Output */

2014-09-02T21:13:59Z

Output

← Older revision		Revision as of 21:13, 2 September 2014
Line 29:		Line 29:

	==Output==		==Output==
	JANUS SSLSTATUS provides the following information:		<var>JANUS SSLSTATUS</var> provides the following information:
	<table>		<table>
	<tr><th><var>Name</var></th>		<tr><th><var>Name</var></th>
Line 66:		Line 66:
	<td>The number of times a browser tried to continue an SSL/TLS session but Janus decided that the session information in its session cache had expired.		<td>The number of times a browser tried to continue an SSL/TLS session but Janus decided that the session information in its session cache had expired.
	<p>		<p>
	These timeouts are only likely to happen if the default SSL session life-spans are overridden with the <var>[[SSLMAXAGE parameter\|SSLMAXAGE]]</var> parameter on the <var>JANUS DEFINE</var> command. If SSLMAXAGE is not defined, both Janus and the other side of an encrypted connection are likely to be using the same default life-spans for secure sessions: 2 minutes for SSL V2, and 24 hours for SSL V3 and TLS. </p>		These timeouts are only likely to happen if the default SSL session life-spans are overridden with the <var>[[SSLMAXAGE (JANUS DEFINE parameter)\|SSLMAXAGE]]</var> parameter on the <var>JANUS DEFINE</var> command. If <var>SSLMAXAGE</var> is not defined, both Janus and the other side of an encrypted connection are likely to be using the same default life-spans for secure sessions: 2 minutes for SSL V2, and 24 hours for SSL V3 and TLS. </p>
	<p>		<p>
	If both client and server have identical values for the maximum SSL/TLS session life-span, there is a slight chance that a client will decide that a secure session is still valid (by say one millisecond), but the delay between this and the time the server receives the request is long enough for the server to decide the session is expired. Even so, an expired session simply forces the client and server to start a new session by exchanging a new "master-secret" using public-key/private-key encryption/decryption. Otherwise, processing continues as usual over the connection.</p></td></tr>		If both client and server have identical values for the maximum SSL/TLS session life-span, there is a slight chance that a client will decide that a secure session is still valid (by say one millisecond), but the delay between this and the time the server receives the request is long enough for the server to decide the session is expired. Even so, an expired session simply forces the client and server to start a new session by exchanging a new "master-secret" using public-key/private-key encryption/decryption. Otherwise, processing continues as usual over the connection.</p></td></tr>

JAL: /* Output */

2013-04-16T19:01:03Z

Output

← Older revision		Revision as of 19:01, 16 April 2013
Line 66:		Line 66:
	<td>The number of times a browser tried to continue an SSL/TLS session but Janus decided that the session information in its session cache had expired.		<td>The number of times a browser tried to continue an SSL/TLS session but Janus decided that the session information in its session cache had expired.
	<p>		<p>
	These timeouts are only likely to happen if the default SSL session life-spans are overridden with the SSLMAXAGE parameter () on the JANUS DEFINE command. If SSLMAXAGE is not defined, both Janus and the other side of an encrypted connection are likely to be using the same default life-spans for secure sessions: 2 minutes for SSL V2, and 24 hours for SSL V3 and TLS. </p>		These timeouts are only likely to happen if the default SSL session life-spans are overridden with the <var>[[SSLMAXAGE parameter\|SSLMAXAGE]]</var> parameter on the <var>JANUS DEFINE</var> command. If SSLMAXAGE is not defined, both Janus and the other side of an encrypted connection are likely to be using the same default life-spans for secure sessions: 2 minutes for SSL V2, and 24 hours for SSL V3 and TLS. </p>
	<p>		<p>
	If both client and server have identical values for the maximum SSL/TLS session life-span, there is a slight chance that a client will decide that a secure session is still valid (by say one millisecond), but the delay between this and the time the server receives the request is long enough for the server to decide the session is expired. Even so, an expired session simply forces the client and server to start a new session by exchanging a new "master-secret" using public-key/private-key encryption/decryption. Otherwise, processing continues as usual over the connection.</p></td></tr>		If both client and server have identical values for the maximum SSL/TLS session life-span, there is a slight chance that a client will decide that a secure session is still valid (by say one millisecond), but the delay between this and the time the server receives the request is long enough for the server to decide the session is expired. Even so, an expired session simply forces the client and server to start a new session by exchanging a new "master-secret" using public-key/private-key encryption/decryption. Otherwise, processing continues as usual over the connection.</p></td></tr>

JAL at 18:57, 16 April 2013

2013-04-16T18:57:55Z

← Older revision		Revision as of 18:57, 16 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:JANUS SSLSTAT or SSLSTATUS}}		{{DISPLAYTITLE:JANUS SSLSTAT or SSLSTATUS}}
	<span class="pageSubtitle">~~SSLSTAT or SSLSTATUS~~</span>		<span class="pageSubtitle">Display SSL activity</span>

	JANUS SSLSTAT and JANUS SSLSTATUS are simply two ways of issuing the same command. The JANUS SSLSTAT or SSLSTATUS command provides a detailed display of the SSL activity for each combination of Janus port and network security protocol. "SSL activity" refers to ''[http://www.sirius-software.com/maint/download/jansslr.pdf Janus Network Security]'' encrypted communications on a Janus port whose definition includes an SSL parameter specification. <var class="product">Janus Network Security</var> supports the SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols.		JANUS SSLSTAT and JANUS SSLSTATUS are simply two ways of issuing the same command. The JANUS SSLSTAT or SSLSTATUS command provides a detailed display of the SSL activity for each combination of Janus port and network security protocol. "SSL activity" refers to ''[http://www.sirius-software.com/maint/download/jansslr.pdf Janus Network Security]'' encrypted communications on a Janus port whose definition includes an SSL parameter specification. <var class="product">Janus Network Security</var> supports the SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols.

JAL at 18:56, 16 April 2013

2013-04-16T18:56:56Z

← Older revision		Revision as of 18:56, 16 April 2013
Line 75:		Line 75:
	By far, the most common cause of these protocol errors is an attempt to connect to a secured port using something other than SSL or TLS: either unencrypted data or an unsupported protocol.</p></td></tr>		By far, the most common cause of these protocol errors is an attempt to connect to a secured port using something other than SSL or TLS: either unencrypted data or an unsupported protocol.</p></td></tr>
	</table>		</table>

			==See also==
			<ul>
			<li>[[List of Janus commands]]
			</ul>

	[[Category:Janus commands\|JANUS SSLSTAT or SSLSTATUS]]		[[Category:Janus commands\|JANUS SSLSTAT or SSLSTATUS]]

JAL: /* Syntax */

2013-04-16T18:47:47Z

Syntax

@@ Line 10: / Line 10: @@
 Where <var class="term">portname</var> is the name of the port(s) to display. <var class="term">portname</var> defaults to an asterisk (<tt>*</tt>) to display the SSL activity on all ports.
-For example, the following command would display the encrypted connection activity on all defined ports:
+For example, the following sample command, which displays the encrypted connection activity on all defined ports, is followed by its output:
-<p class="code">JANUS SSLSTATUS *
+<p class="code">JANUS SSLSTATUS *</p>
 </p>

JAL: /* Output */

2013-04-16T18:34:19Z

Output

← Older revision		Revision as of 18:34, 16 April 2013
Line 17:		Line 17:
	JANUS SSLSTATUS provides the following information:		JANUS SSLSTATUS provides the following information:
	<table>		<table>
	<tr><th>Name</th>		<tr><th><var>Name</var></th>
	<td>Name defined to the TCP/IP port.</td></tr>		<td>Name defined to the TCP/IP port.</td></tr>

	<tr><th>Port</th>		<tr><th><var>Port</var></th>
	<td>TCP/IP port number.</td></tr>		<td>TCP/IP port number.</td></tr>

	<tr><th>Type</th>		<tr><th><var>Type</var></th>
	<td>IFDIAL, SDS, OAS, OMNI, OPENSERV, WEBSERV, CLSOCK, or SRVSOCK.</td></tr>		<td>IFDIAL, SDS, OAS, OMNI, OPENSERV, WEBSERV, CLSOCK, or SRVSOCK.</td></tr>

	<tr><th>Stat</th>		<tr><th><var>Stat</var></th>
	<td>Status of the connection (started, stopped, forcing, or draining).</td></tr>		<td>Status of the connection (started, stopped, forcing, or draining).</td></tr>

	<tr><th>Prot</th>		<tr><th><var>Prot</var></th>
	<td>The security protocol to which the line applies. ~~:br~~ One line is displayed for each port for each protocol. Currently, the supported protocols are SSL version 2 (V2), SSL V3, and TLS V1.</td></tr>		<td>The security protocol to which the line applies.
			<p>
			One line is displayed for each port for each protocol. Currently, the supported protocols are SSL version 2 (V2), SSL V3, and TLS V1.</p></td></tr>

	<tr><th>Connects</th>		<tr><th><var>Connects</var></th>
	<td>Number of TCP/IP connections made to the port. ~~:br~~ For a WEBSERV port, this corresponds to the number of "hits" or pages requested from the server.</td></tr>		<td>Number of TCP/IP connections made to the port.
			<p>
			For a WEBSERV port, this corresponds to the number of "hits" or pages requested from the server.</p></td></tr>

	<tr><th>SesNew</th>		<tr><th><var>SesNew</var></th>
	<td>Number of new SSL/TLS sessions created for the port. ~~:br~~ SesNew is always less than Connects, because the worst case is that each new connection requires a new session. A new session requires the exchange of a "master-secret" using computationally expensive public-key/private-key encryption/decryption. Because of the cost of this exchange, most SSL/TLS implementations try to re-use a master-secret from a previous connection. All connections that use the same master-secret are part of an SSL/TLS session. Ideally, SesNew would be significantly less than Connects.</td></tr>		<td>Number of new SSL/TLS sessions created for the port.
			<p>
			SesNew is always less than Connects, because the worst case is that each new connection requires a new session. A new session requires the exchange of a "master-secret" using computationally expensive public-key/private-key encryption/decryption. Because of the cost of this exchange, most SSL/TLS implementations try to re-use a master-secret from a previous connection. All connections that use the same master-secret are part of an SSL/TLS session. Ideally, SesNew would be significantly less than Connects.</p></td></tr>

	<tr><th>SesNF</th>		<tr><th><var>SesNF</var></th>
	<td>The number of times a browser tried to continue an SSL/TLS session but Janus was unable to locate the session information in its session cache. This not-found situation is only likely to happen if the session information was displaced from the session cache by other sessions. If SesNF is a large value, it might be worth increasing the size of the SSL session cache with the SSLCACHE parameter () on the JANUS DEFINE command. While from a client's perspective, a session-not-found situation can also occur if the port (or possibly the Online) serving the connection was cycled since the last connection by the client, this is not counted as part of SesNF.</td></tr>		<td>The number of times a browser tried to continue an SSL/TLS session but Janus was unable to locate the session information in its session cache.
			<p>
			This not-found situation is only likely to happen if the session information was displaced from the session cache by other sessions. If SesNF is a large value, it might be worth increasing the size of the SSL session cache with the <var>[[SSLCACHE (JANUS DEFINE parameter)\|SSLCACHE]]</var> on the <var>JANUS DEFINE</var> command. While from a client's perspective, a session-not-found situation can also occur if the port (or possibly the Online) serving the connection was cycled since the last connection by the client, this is not counted as part of SesNF.</p></td></tr>

	<tr><th>SesTO</th>		<tr><th><var>SesTO</var></th>
	<td>The number of times a browser tried to continue an SSL/TLS session but Janus decided that the session information in its session cache had expired.		<td>The number of times a browser tried to continue an SSL/TLS session but Janus decided that the session information in its session cache had expired.
	<p>		<p>
Line 48:		Line 56:
	If both client and server have identical values for the maximum SSL/TLS session life-span, there is a slight chance that a client will decide that a secure session is still valid (by say one millisecond), but the delay between this and the time the server receives the request is long enough for the server to decide the session is expired. Even so, an expired session simply forces the client and server to start a new session by exchanging a new "master-secret" using public-key/private-key encryption/decryption. Otherwise, processing continues as usual over the connection.</p></td></tr>		If both client and server have identical values for the maximum SSL/TLS session life-span, there is a slight chance that a client will decide that a secure session is still valid (by say one millisecond), but the delay between this and the time the server receives the request is long enough for the server to decide the session is expired. Even so, an expired session simply forces the client and server to start a new session by exchanging a new "master-secret" using public-key/private-key encryption/decryption. Otherwise, processing continues as usual over the connection.</p></td></tr>

	<tr><th>Errs</th>		<tr><th><var>Errs</var></th>
	<td>The number of security protocol errors.		<td>The number of security protocol errors.
	<p>		<p>

JAL: /* Output */

2013-04-16T18:26:19Z

Output

← Older revision		Revision as of 18:26, 16 April 2013
Line 16:		Line 16:
	==Output==		==Output==
	JANUS SSLSTATUS provides the following information:		JANUS SSLSTATUS provides the following information:
	<table ~~class="syntaxTable"~~>		<table>
	<tr><th>Name</th>		<tr><th>Name</th>
	<td>Name defined to the TCP/IP port.</td></tr>		<td>Name defined to the TCP/IP port.</td></tr>
Line 49:		Line 49:

	<tr><th>Errs</th>		<tr><th>Errs</th>
	<td>The number of security protocol errors. ~~.br~~ By far, the most common cause of these protocol errors is an attempt to connect to a secured port using something other than SSL or TLS: either unencrypted data or an unsupported protocol.		<td>The number of security protocol errors.
	</td></tr></table>		<p>
			By far, the most common cause of these protocol errors is an attempt to connect to a secured port using something other than SSL or TLS: either unencrypted data or an unsupported protocol.</p></td></tr>
			</table>

	[[Category:Janus commands\|JANUS SSLSTAT or SSLSTATUS]]		[[Category:Janus commands\|JANUS SSLSTAT or SSLSTATUS]]

JALWiccan: Automatically generated page update

2013-04-16T17:32:05Z

Automatically generated page update

← Older revision		Revision as of 17:32, 16 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:JANUS SSLSTAT or SSLSTATUS}}		{{DISPLAYTITLE:JANUS SSLSTAT or SSLSTATUS}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>SSLSTAT or SSLSTATUS~~<section end="desc" />~~</span>		<span class="pageSubtitle">SSLSTAT or SSLSTATUS</span>

	JANUS SSLSTAT and JANUS SSLSTATUS are simply two ways of issuing the same command. The JANUS SSLSTAT or SSLSTATUS command provides a detailed display of the SSL activity for each combination of Janus port and network security protocol. "SSL activity" refers to ''[http://www.sirius-software.com/maint/download/jansslr.pdf Janus Network Security]'' encrypted communications on a Janus port whose definition includes an SSL parameter specification. <var class="product">Janus Network Security</var> supports the SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols.		JANUS SSLSTAT and JANUS SSLSTATUS are simply two ways of issuing the same command. The JANUS SSLSTAT or SSLSTATUS command provides a detailed display of the SSL activity for each combination of Janus port and network security protocol. "SSL activity" refers to ''[http://www.sirius-software.com/maint/download/jansslr.pdf Janus Network Security]'' encrypted communications on a Janus port whose definition includes an SSL parameter specification. <var class="product">Janus Network Security</var> supports the SSL (Secure Sockets Layer) and TLS (Transport Layer Security) protocols.

	==Syntax==		==Syntax==
	<p class="syntax"~~><section begin="syntax" /~~>JANUS SSLSTATUS portname		<p class="syntax">JANUS SSLSTATUS portname
	~~<section end="syntax" />~~</p>		</p>

	Where <var class="term">portname</var> is the name of the port(s) to display. <var class="term">portname</var> defaults to an asterisk (<tt>*</tt>) to display the SSL activity on all ports.		Where <var class="term">portname</var> is the name of the port(s) to display. <var class="term">portname</var> defaults to an asterisk (<tt>*</tt>) to display the SSL activity on all ports.