SSLCACHE (JANUS DEFINE parameter) - Revision history

JAL at 20:27, 14 October 2014

2014-10-14T20:27:01Z

← Older revision		Revision as of 20:27, 14 October 2014
Line 11:		Line 11:
	Each session requires approximately 512 bytes per entry to cache session related information. A further <var>[[SSLMAXCERTL (JANUS DEFINE parameter)\|SSLMAXCERTL]]</var> bytes are required to hold server certificates for <var>[[JANUS DEFINE#type\|CLSOCK]]</var> ports, or to hold client certificates for Janus server ports that request them by including <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERT]]</var> or <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERTR]]</var>.		Each session requires approximately 512 bytes per entry to cache session related information. A further <var>[[SSLMAXCERTL (JANUS DEFINE parameter)\|SSLMAXCERTL]]</var> bytes are required to hold server certificates for <var>[[JANUS DEFINE#type\|CLSOCK]]</var> ports, or to hold client certificates for Janus server ports that request them by including <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERT]]</var> or <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERTR]]</var>.

	If the <var>SSLCACHE</var> value is too small, and a larger than anticipated number of users attempt to access an SSL-secured port, entries in the cache are removed on a least-recently-used basis. This may lead to greater overhead for re-execution of the CPU intensive initial public-key/private-key encryption/decryption operations. The indicator that the <var>SSLCACHE</var> value is not large enough to hold all the contemporaneous SSL sessions is a non-zero value in the "SesNF" column of the <var>[[JANUS SSLSTAT]]</var> command result. This is not necessarily problematic as long as the SesNF value is relatively small, because it is not unreasonable to suffer an occasional lost session in order to reduce virtual storage.		If the <var>SSLCACHE</var> value is too small, and a larger than anticipated number of users attempt to access an SSL-secured port, entries in the cache are removed on a least-recently-used basis. This may lead to greater overhead for re-execution of the CPU intensive initial public-key/private-key encryption/decryption operations. The indicator that the <var>SSLCACHE</var> value is not large enough to hold all the contemporaneous SSL sessions is a non-zero value in the "SesNF" column of the <var>[[JANUS SSLSTAT or SSLSTATUS\|JANUS SSLSTAT]]</var> command result. This is not necessarily problematic as long as the SesNF value is relatively small, because it is not unreasonable to suffer an occasional lost session in order to reduce virtual storage.

	'''Note:''' <var>SSLCACHE</var> is specified in '''entries''', and the default <var>SSLCACHE</var> allocation is the number of storage entries required for 16 times the number of threads defined on the port. So by default, 10 threads would result in 160 entries; at 512 bytes per entry, this would require 81,920 bytes of virtual storage. 100 threads would require 819,200 bytes.		<p class="note">'''Note:''' <var>SSLCACHE</var> is specified in '''entries''', and the default <var>SSLCACHE</var> allocation is the number of storage entries required for 16 times the number of threads defined on the port. So by default, 10 threads would result in 160 entries; at 512 bytes per entry, this would require 81,920 bytes of virtual storage. 100 threads would require 819,200 bytes. </p>

	The default <var>SSLCACHE</var> value is likely to be excessively large for <var>CLSOCK</var> ports that only connect to a single or to a few servers. All <var>CLSOCK</var> connections to a particular server use the same SSL session regardless of how many different threads initiate connections.		The default <var>SSLCACHE</var> value is likely to be excessively large for <var>CLSOCK</var> ports that only connect to a single or to a few servers. All <var>CLSOCK</var> connections to a particular server use the same SSL session regardless of how many different threads initiate connections.

JALWiccan: Automatically generated page update

2013-04-16T22:24:07Z

Automatically generated page update

← Older revision		Revision as of 22:24, 16 April 2013
Line 1:		Line 1:
	<span class="pageSubtitle"~~><section begin="desc" /~~>SSLCACHE xxxx — number of cache entries for SSL sessions~~<section end="desc" />~~</span>		<span class="pageSubtitle">SSLCACHE xxxx — number of cache entries for SSL sessions</span>

	<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 22:46, 1 March 2012

2012-03-01T22:46:47Z

← Older revision		Revision as of 22:46, 1 March 2012
Line 1:		Line 1:
	<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx &~~amp;~~mdash; number of cache entries for SSL sessions<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx — number of cache entries for SSL sessions<section end="desc" /></span>

	<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.
Line 11:		Line 11:
	Each session requires approximately 512 bytes per entry to cache session related information. A further <var>[[SSLMAXCERTL (JANUS DEFINE parameter)\|SSLMAXCERTL]]</var> bytes are required to hold server certificates for <var>[[JANUS DEFINE#type\|CLSOCK]]</var> ports, or to hold client certificates for Janus server ports that request them by including <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERT]]</var> or <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERTR]]</var>.		Each session requires approximately 512 bytes per entry to cache session related information. A further <var>[[SSLMAXCERTL (JANUS DEFINE parameter)\|SSLMAXCERTL]]</var> bytes are required to hold server certificates for <var>[[JANUS DEFINE#type\|CLSOCK]]</var> ports, or to hold client certificates for Janus server ports that request them by including <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERT]]</var> or <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERTR]]</var>.

	If the <var>SSLCACHE</var> value is too small, and a larger than anticipated number of users attempt to access an SSL-secured port, entries in the cache are removed on a least-recently-used basis. This may lead to greater overhead for re-execution of the CPU intensive initial public-key/private-key encryption/decryption operations. The indicator that the <var>SSLCACHE</var> value is not large enough to hold all the contemporaneous SSL sessions is a non-zero value in the "SesNF" column of the <var>~~ÝÝJANUS~~ SSLSTAT]]</var> command result. This is not necessarily problematic as long as the SesNF value is relatively small, because it is not unreasonable to suffer an occasional lost session in order to reduce virtual storage.		If the <var>SSLCACHE</var> value is too small, and a larger than anticipated number of users attempt to access an SSL-secured port, entries in the cache are removed on a least-recently-used basis. This may lead to greater overhead for re-execution of the CPU intensive initial public-key/private-key encryption/decryption operations. The indicator that the <var>SSLCACHE</var> value is not large enough to hold all the contemporaneous SSL sessions is a non-zero value in the "SesNF" column of the <var>[[JANUS SSLSTAT]]</var> command result. This is not necessarily problematic as long as the SesNF value is relatively small, because it is not unreasonable to suffer an occasional lost session in order to reduce virtual storage.

	'''Note:''' <var>SSLCACHE</var> is specified in '''entries''', and the default <var>SSLCACHE</var> allocation is the number of storage entries required for 16 times the number of threads defined on the port. So by default, 10 threads would result in 160 entries; at 512 bytes per entry, this would require 81,920 bytes of virtual storage. 100 threads would require 819,200 bytes.		'''Note:''' <var>SSLCACHE</var> is specified in '''entries''', and the default <var>SSLCACHE</var> allocation is the number of storage entries required for 16 times the number of threads defined on the port. So by default, 10 threads would result in 160 entries; at 512 bytes per entry, this would require 81,920 bytes of virtual storage. 100 threads would require 819,200 bytes.

JALWiccan: 1 revision

2012-03-01T22:42:46Z

1 revision

← Older revision	Revision as of 22:42, 1 March 2012
(No difference)

JAL2 at 22:42, 1 March 2012

2012-03-01T22:42:45Z

← Older revision		Revision as of 22:42, 1 March 2012
Line 1:		Line 1:
	<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx — number of cache entries for SSL sessions<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx &mdash; number of cache entries for SSL sessions<section end="desc" /></span>

	<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.
Line 11:		Line 11:
	Each session requires approximately 512 bytes per entry to cache session related information. A further <var>[[SSLMAXCERTL (JANUS DEFINE parameter)\|SSLMAXCERTL]]</var> bytes are required to hold server certificates for <var>[[JANUS DEFINE#type\|CLSOCK]]</var> ports, or to hold client certificates for Janus server ports that request them by including <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERT]]</var> or <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERTR]]</var>.		Each session requires approximately 512 bytes per entry to cache session related information. A further <var>[[SSLMAXCERTL (JANUS DEFINE parameter)\|SSLMAXCERTL]]</var> bytes are required to hold server certificates for <var>[[JANUS DEFINE#type\|CLSOCK]]</var> ports, or to hold client certificates for Janus server ports that request them by including <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERT]]</var> or <var>[[SSLCLCERT and SSLCLCERTR (JANUS DEFINE parameters)\|SSLCLCERTR]]</var>.

	If the <var>SSLCACHE</var> value is too small, and a larger than anticipated number of users attempt to access an SSL-secured port, entries in the cache are removed on a least-recently-used basis. This may lead to greater overhead for re-execution of the CPU intensive initial public-key/private-key encryption/decryption operations. The indicator that the <var>SSLCACHE</var> value is not large enough to hold all the contemporaneous SSL sessions is a non-zero value in the "SesNF" column of the ~~[[JANUS~~ SSLSTAT]] command result. This is not necessarily problematic as long as the SesNF value is relatively small, because it is not unreasonable to suffer an occasional lost session in order to reduce virtual storage.		If the <var>SSLCACHE</var> value is too small, and a larger than anticipated number of users attempt to access an SSL-secured port, entries in the cache are removed on a least-recently-used basis. This may lead to greater overhead for re-execution of the CPU intensive initial public-key/private-key encryption/decryption operations. The indicator that the <var>SSLCACHE</var> value is not large enough to hold all the contemporaneous SSL sessions is a non-zero value in the "SesNF" column of the <var>ÝÝJANUS SSLSTAT]]</var> command result. This is not necessarily problematic as long as the SesNF value is relatively small, because it is not unreasonable to suffer an occasional lost session in order to reduce virtual storage.

	'''Note:''' <var>SSLCACHE</var> is specified in '''entries''', and the default <var>SSLCACHE</var> allocation is the number of storage entries required for 16 times the number of threads defined on the port. So by default, 10 threads would result in 160 entries; at 512 bytes per entry, this would require 81,920 bytes of virtual storage. 100 threads would require 819,200 bytes.		'''Note:''' <var>SSLCACHE</var> is specified in '''entries''', and the default <var>SSLCACHE</var> allocation is the number of storage entries required for 16 times the number of threads defined on the port. So by default, 10 threads would result in 160 entries; at 512 bytes per entry, this would require 81,920 bytes of virtual storage. 100 threads would require 819,200 bytes.

JAL2 at 22:51, 29 February 2012

2012-02-29T22:51:20Z

← Older revision		Revision as of 22:51, 29 February 2012
Line 1:		Line 1:

	<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx — number of cache entries for SSL sessions<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx — number of cache entries for SSL sessions<section end="desc" /></span>

Line 18:		Line 17:
	The default <var>SSLCACHE</var> value is likely to be excessively large for <var>CLSOCK</var> ports that only connect to a single or to a few servers. All <var>CLSOCK</var> connections to a particular server use the same SSL session regardless of how many different threads initiate connections.		The default <var>SSLCACHE</var> value is likely to be excessively large for <var>CLSOCK</var> ports that only connect to a single or to a few servers. All <var>CLSOCK</var> connections to a particular server use the same SSL session regardless of how many different threads initiate connections.

	<var>SSLCACHE</var> is valid for <var>[[JANUS DEFINE#type\|SRVSOCK]]</var>, CLSOCK (but not DEBUGGERCLIENT), <var>[[JANUS DEFINE#type\|WEBSERV]]</var>, <var>[[JANUS DEFINE#type\|OPENSERV]]</var>, and <var>[[JANUS DEFINE#type\|SDS]]</var> port types.		<var>SSLCACHE</var> is valid for <var>[[JANUS DEFINE#type\|SRVSOCK]]</var>, <var>CLSOCK</var> (but not <var>[[JANUS DEFINE#type\|DEBUGGERCLIENT]]</var>, <var>[[JANUS DEFINE#type\|WEBSERV]]</var>, <var>[[JANUS DEFINE#type\|OPENSERV]]</var>, and <var>[[JANUS DEFINE#type\|SDS]]</var> port types.

	==See also==		==See also==

JAL2 at 22:49, 29 February 2012

2012-02-29T22:49:17Z

← Older revision		Revision as of 22:49, 29 February 2012
Line 1:		Line 1:
	~~{{DISPLAYTITLE:SSLCACHE}}~~
	<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx -- number of cache entries for SSL sessions<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx — number of cache entries for SSL sessions<section end="desc" /></span>

	<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JAL2 at 22:48, 29 February 2012

2012-02-29T22:48:57Z

← Older revision		Revision as of 22:48, 29 February 2012
Line 16:		Line 16:
	'''Note:''' <var>SSLCACHE</var> is specified in '''entries''', and the default <var>SSLCACHE</var> allocation is the number of storage entries required for 16 times the number of threads defined on the port. So by default, 10 threads would result in 160 entries; at 512 bytes per entry, this would require 81,920 bytes of virtual storage. 100 threads would require 819,200 bytes.		'''Note:''' <var>SSLCACHE</var> is specified in '''entries''', and the default <var>SSLCACHE</var> allocation is the number of storage entries required for 16 times the number of threads defined on the port. So by default, 10 threads would result in 160 entries; at 512 bytes per entry, this would require 81,920 bytes of virtual storage. 100 threads would require 819,200 bytes.

	The default <var>SSLCACHE</var> value is likely to be excessively large for <var>~~[[JANUS DEFINE#type\|~~CLSOCK]]</var> ports that only connect to a single or to a few servers. All CLSOCK connections to a particular server use the same SSL session regardless of how many different threads initiate connections.		The default <var>SSLCACHE</var> value is likely to be excessively large for <var>CLSOCK</var> ports that only connect to a single or to a few servers. All <var>CLSOCK</var> connections to a particular server use the same SSL session regardless of how many different threads initiate connections.

	<var>SSLCACHE</var> is valid for <var>[[JANUS DEFINE#type\|SRVSOCK]]</var>, CLSOCK (but not DEBUGGERCLIENT), <var>[[JANUS DEFINE#type\|WEBSERV]]</var>, <var>[[JANUS DEFINE#type\|OPENSERV]]</var>, and <var>[[JANUS DEFINE#type\|SDS]]</var> port types.		<var>SSLCACHE</var> is valid for <var>[[JANUS DEFINE#type\|SRVSOCK]]</var>, CLSOCK (but not DEBUGGERCLIENT), <var>[[JANUS DEFINE#type\|WEBSERV]]</var>, <var>[[JANUS DEFINE#type\|OPENSERV]]</var>, and <var>[[JANUS DEFINE#type\|SDS]]</var> port types.

	==See also==		==See also==

	<ul>		<ul>
	<li>[[List of Janus commands]]		<li>[[List of Janus commands]]

JALWiccan: 1 revision

2012-02-29T22:33:27Z

1 revision

← Older revision	Revision as of 22:33, 29 February 2012
(No difference)

JALWiccan: 1 revision

2012-02-29T22:33:19Z

1 revision

← Older revision		Revision as of 22:33, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx -- number of cache entries for SSL sessions<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />SSLCACHE xxxx -- number of cache entries for SSL sessions<section end="desc" /></span>

	<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port~~. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]~~.		<var>SSLCACHE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter specifies the number of entries in virtual storage to be allocated for caching information related to this port's SSL sessions. A Janus port whose definition includes an <var>[[SSL (JANUS DEFINE parameter)\|SSL]]</var> parameter supports <var class="product">[http://sirius-software.com/maint/download/jansslr.pdf Janus Network Security]</var> SSL (Secure Sockets Layer) or TLS (Transport Layer Security) encrypted sessions.		This parameter specifies the number of entries in virtual storage to be allocated for caching information related to this port's SSL sessions. A Janus port whose definition includes an <var>[[SSL (JANUS DEFINE parameter)\|SSL]]</var> parameter supports <var class="product">[http://sirius-software.com/maint/download/jansslr.pdf Janus Network Security]</var> SSL (Secure Sockets Layer) or TLS (Transport Layer Security) encrypted sessions.