JANUS ADDCA - Revision history

JAL: link repair

2016-08-30T19:22:03Z

link repair

← Older revision		Revision as of 19:22, 30 August 2016
Line 6:		Line 6:
	"Added" certificates are used for authentication (decryption) of incoming certificates, that is, to verify that a certificate presented to the port bears the authentic signature of the certifying authority. Such an incoming certificate may be a server certificate sent in reply to a <var>CLSOCK</var> port, or it may be a client certificate sent in reply to a <var>SRVSOCK</var>, <var>WEBSERV</var>, <var>SDS</var> or <var>OPENSERV</var> port.		"Added" certificates are used for authentication (decryption) of incoming certificates, that is, to verify that a certificate presented to the port bears the authentic signature of the certifying authority. Such an incoming certificate may be a server certificate sent in reply to a <var>CLSOCK</var> port, or it may be a client certificate sent in reply to a <var>SRVSOCK</var>, <var>WEBSERV</var>, <var>SDS</var> or <var>OPENSERV</var> port.

	<var class="product">[[~~Media:jansslrNew.pdf\|~~Janus Network Security]] accepts only incoming certificates that are "signed" by a trusted certifying authority (often abbreviated as CA). Applications can place further restrictions on acceptable certificates but cannot relax this restriction.		<var class="product">[[Janus Network Security]] accepts only incoming certificates that are "signed" by a trusted certifying authority (often abbreviated as CA). Applications can place further restrictions on acceptable certificates but cannot relax this restriction.

	The <var class="product">SOUL</var> <var>ADDCA</var> utility lets you add multiple certificates from the [[RKTools]] <code>SIRIUS</code> file, as described in [[JANUS ADDCA#Adding SIRIUS-file certificates\|Adding SIRIUS-file certificates]].		The <var class="product">SOUL</var> <var>ADDCA</var> utility lets you add multiple certificates from the [[RKTools]] <code>SIRIUS</code> file, as described in [[JANUS ADDCA#Adding SIRIUS-file certificates\|Adding SIRIUS-file certificates]].

JAL: minor formatting

2016-08-30T19:20:30Z

minor formatting

← Older revision		Revision as of 19:20, 30 August 2016
Line 8:		Line 8:
	<var class="product">[[Media:jansslrNew.pdf\|Janus Network Security]] accepts only incoming certificates that are "signed" by a trusted certifying authority (often abbreviated as CA). Applications can place further restrictions on acceptable certificates but cannot relax this restriction.		<var class="product">[[Media:jansslrNew.pdf\|Janus Network Security]] accepts only incoming certificates that are "signed" by a trusted certifying authority (often abbreviated as CA). Applications can place further restrictions on acceptable certificates but cannot relax this restriction.

	The <var class="product">SOUL</var> <~~code~~>ADDCA</~~code~~> utility lets you add multiple certificates from the [[RKTools]] <code>SIRIUS</code> file, as described in [[JANUS ADDCA#Adding SIRIUS-file certificates\|Adding SIRIUS-file certificates]].		The <var class="product">SOUL</var> <var>ADDCA</var> utility lets you add multiple certificates from the [[RKTools]] <code>SIRIUS</code> file, as described in [[JANUS ADDCA#Adding SIRIUS-file certificates\|Adding SIRIUS-file certificates]].

	==Syntax==		==Syntax==
Line 65:		Line 65:

	To view the list of trusted certificates and their contents, use the <var>[[JANUS DISPLAYCA]]</var> command. To view the number of received certificates signed by each trusted CA, use the <var>[[JANUS STATUSCA]]</var> command.		To view the list of trusted certificates and their contents, use the <var>[[JANUS DISPLAYCA]]</var> command. To view the number of received certificates signed by each trusted CA, use the <var>[[JANUS STATUSCA]]</var> command.

	~~For more information about certificates and certifying authorities, see the <var class="book">[[Media:jansslrNew.pdf\|Janus Network Security Reference Manual]]</var>.~~

	==Adding SIRIUS-file certificates==		==Adding SIRIUS-file certificates==
Line 75:		Line 73:
	The certificates are procedures whose names have the prefix <code>CA_</code> so they are easy to scan using a <var>DISPLAY PROCEDURE</var> command or by browsing the procedures in [[SirPro]]. Sirius will periodically review the certificates loaded to <code>SIRIUS</code>, eliminate any that have expired, and load new ones when they are made available by various well-accepted CAs.		The certificates are procedures whose names have the prefix <code>CA_</code> so they are easy to scan using a <var>DISPLAY PROCEDURE</var> command or by browsing the procedures in [[SirPro]]. Sirius will periodically review the certificates loaded to <code>SIRIUS</code>, eliminate any that have expired, and load new ones when they are made available by various well-accepted CAs.

	The <var class="product">~~User Language~~</var> <~~code~~>ADDCA</~~code~~> utility lets you add some or all of these certificates at once to an SSL port. The utility is invoked at the command level ~~via~~ <code>INCLUDE</code>:		The <var class="product">SOUL</var> <var>ADDCA</var> utility lets you add some or all of these certificates at once to an SSL port. The utility is invoked at the command level with <code>INCLUDE</code>:

	<p class="syntax">IN SIRIUS INCLUDE ADDCA <span class="term">portname certificate</span>		<p class="syntax">IN SIRIUS INCLUDE ADDCA <span class="term">portname certificate</span>
Line 102:		Line 100:
	<p class="note">'''Note:''' The CA certificates are stored as procedures with mixed-case names, which makes them much easier to scan visually, but a little more difficult to manipulate. </p>		<p class="note">'''Note:''' The CA certificates are stored as procedures with mixed-case names, which makes them much easier to scan visually, but a little more difficult to manipulate. </p>

	For instance, if the above <var>INCLUDE</var> command is used, all the intended certificates are loaded, because the <code>CA_T</code> in uppercase matches the case of the corresponding characters in the certificate names. But if you want a more precise search and the name to be matched by the pattern includes mixed-case characters, the <~~code~~>INCLUDE</~~code~~> command must be bracketed with a set of <~~code~~>LOWER/UPPER</~~code~~> commands, as in:		For instance, if the above <var>INCLUDE</var> command is used, all the intended certificates are loaded, because the <code>CA_T</code> in uppercase matches the case of the corresponding characters in the certificate names. But if you want a more precise search and the name to be matched by the pattern includes mixed-case characters, the <var>INCLUDE</var> command must be bracketed with a set of <var>LOWER</var>/<var>UPPER</var> commands, as in:

	<p class="code">JANUS DEFINE MYSSLPORT * CLSOCK 10		<p class="code">JANUS DEFINE MYSSLPORT * CLSOCK 10

JAL: minor formatting

2016-05-25T21:39:08Z

minor formatting

← Older revision		Revision as of 21:39, 25 May 2016
Line 11:		Line 11:

	==Syntax==		==Syntax==
	<p class="syntax">JANUS ADDCA portname filename procname		<p class="syntax">JANUS ADDCA <span class="term">portname filename procname</span>
	</p>		</p>

	Where each parameter is positional and required:		Where each parameter is positional and required:

	<table ~~class="syntaxTable"~~>		<table>
	<tr><th>portname</th>		<tr><th>portname</th>
	<td>The defined Janus port to which the certificate is to be added. Can include wildcards. Non-SSL ports will not have trusted CA certificates added to them, since it is meaningless to have trusted CAs on a non-SSL port.</td></tr>		<td>The defined Janus port to which the certificate is to be added. Can include wildcards. Non-SSL ports will not have trusted CA certificates added to them, since it is meaningless to have trusted CAs on a non-SSL port.</td></tr>

JAL: minor cleanup

2015-10-23T21:18:39Z

minor cleanup

← Older revision		Revision as of 21:18, 23 October 2015
Line 8:		Line 8:
	<var class="product">[[Media:jansslrNew.pdf\|Janus Network Security]] accepts only incoming certificates that are "signed" by a trusted certifying authority (often abbreviated as CA). Applications can place further restrictions on acceptable certificates but cannot relax this restriction.		<var class="product">[[Media:jansslrNew.pdf\|Janus Network Security]] accepts only incoming certificates that are "signed" by a trusted certifying authority (often abbreviated as CA). Applications can place further restrictions on acceptable certificates but cannot relax this restriction.

	The <var class="product">~~User Language~~</var> <code>ADDCA</code> utility lets you add multiple certificates from the [[RKTools]] <code>SIRIUS</code> file, as described in [[JANUS ADDCA#Adding SIRIUS-file certificates\|Adding SIRIUS-file certificates]].		The <var class="product">SOUL</var> <code>ADDCA</code> utility lets you add multiple certificates from the [[RKTools]] <code>SIRIUS</code> file, as described in [[JANUS ADDCA#Adding SIRIUS-file certificates\|Adding SIRIUS-file certificates]].

	==Syntax==		==Syntax==
Line 69:		Line 69:

	==Adding SIRIUS-file certificates==		==Adding SIRIUS-file certificates==
	Although a server port is not likely to need to use the <var>JANUS ADDCA</var> command more than once, a client port may want to use it to add multiple certificates. As a convenience especially for a <var>CLSOCK</var> port connecting to an SSL server, ~~Sirius~~ pre-loads a set of standard certifying authorities' certificates to the <code>SIRIUS</code> procedure file ~~(as of ''[[UL/SPF]]'' 7.3)~~. ''[[Janus Sockets]]'' SSL client ports need to add the certificate(s) of the CA that signed the certificate of the server or servers to which the client will connect. (Janus does not allow a port to specify exceptions, that is, signed certificates that a port accepts without having the signing CA's certificate.)		Although a server port is not likely to need to use the <var>JANUS ADDCA</var> command more than once, a client port may want to use it to add multiple certificates. As a convenience especially for a <var>CLSOCK</var> port connecting to an SSL server, Rocket pre-loads a set of standard certifying authorities' certificates to the <code>SIRIUS</code> procedure file. [[Janus Sockets]] SSL client ports need to add the certificate(s) of the CA that signed the certificate of the server or servers to which the client will connect. (Janus does not allow a port to specify exceptions, that is, signed certificates that a port accepts without having the signing CA's certificate.)

	The <code>SIRIUS</code> file certificates can be added to a port by the <var>JANUS ADDCA</var> command or by the <code>ADDCA</code> utility, described below. Adding this set of certificates equips the client port in much the same way that internet browsers are equipped with multiple CA certificates.		The <code>SIRIUS</code> file certificates can be added to a port by the <var>JANUS ADDCA</var> command or by the <code>ADDCA</code> utility, described below. Adding this set of certificates equips the client port in much the same way that internet browsers are equipped with multiple CA certificates.

	The certificates are procedures whose names have the prefix <code>CA_</code> so they are easy to scan using a <var>DISPLAY PROCEDURE</var> command or by browsing the procedures in ''[[SirPro]]''. Sirius will periodically review the certificates loaded to <code>SIRIUS</code>, eliminate any that have expired, and load new ones when they are made available by various well-accepted CAs.		The certificates are procedures whose names have the prefix <code>CA_</code> so they are easy to scan using a <var>DISPLAY PROCEDURE</var> command or by browsing the procedures in [[SirPro]]. Sirius will periodically review the certificates loaded to <code>SIRIUS</code>, eliminate any that have expired, and load new ones when they are made available by various well-accepted CAs.

	The <var class="product">User Language</var> <code>ADDCA</code> utility lets you add some or all of these certificates at once to an SSL port. The utility is invoked at the command level via <code>INCLUDE</code>:		The <var class="product">User Language</var> <code>ADDCA</code> utility lets you add some or all of these certificates at once to an SSL port. The utility is invoked at the command level via <code>INCLUDE</code>:

JAL: RKTools replaces UL/SPF

2015-10-23T21:14:08Z

RKTools replaces UL/SPF

← Older revision		Revision as of 21:14, 23 October 2015
Line 6:		Line 6:
	"Added" certificates are used for authentication (decryption) of incoming certificates, that is, to verify that a certificate presented to the port bears the authentic signature of the certifying authority. Such an incoming certificate may be a server certificate sent in reply to a <var>CLSOCK</var> port, or it may be a client certificate sent in reply to a <var>SRVSOCK</var>, <var>WEBSERV</var>, <var>SDS</var> or <var>OPENSERV</var> port.		"Added" certificates are used for authentication (decryption) of incoming certificates, that is, to verify that a certificate presented to the port bears the authentic signature of the certifying authority. Such an incoming certificate may be a server certificate sent in reply to a <var>CLSOCK</var> port, or it may be a client certificate sent in reply to a <var>SRVSOCK</var>, <var>WEBSERV</var>, <var>SDS</var> or <var>OPENSERV</var> port.

	''[~~http~~:~~//www.sirius-software.com/maint/download/jansslr~~.pdf Janus Network Security]'' accepts only incoming certificates that are "signed" by a trusted certifying authority (often abbreviated as CA). Applications can place further restrictions on acceptable certificates but cannot relax this restriction.		<var class="product">[[Media:jansslrNew.pdf\|Janus Network Security]] accepts only incoming certificates that are "signed" by a trusted certifying authority (often abbreviated as CA). Applications can place further restrictions on acceptable certificates but cannot relax this restriction.

	The <var class="product">User Language</var> <code>ADDCA</code> utility~~, available as of Version 7.7 of the ''[[Sirius Mods]]'',~~ lets you add multiple certificates from the ''[[~~UL/SPF~~]]'' <code>SIRIUS</code> file, as described in [[JANUS ADDCA#Adding SIRIUS-file certificates\|"Adding SIRIUS-file certificates"]].		The <var class="product">User Language</var> <code>ADDCA</code> utility lets you add multiple certificates from the [[RKTools]] <code>SIRIUS</code> file, as described in [[JANUS ADDCA#Adding SIRIUS-file certificates\|Adding SIRIUS-file certificates]].

	==Syntax==		==Syntax==
Line 19:		Line 19:
	<tr><th>portname</th>		<tr><th>portname</th>
	<td>The defined Janus port to which the certificate is to be added. Can include wildcards. Non-SSL ports will not have trusted CA certificates added to them, since it is meaningless to have trusted CAs on a non-SSL port.</td></tr>		<td>The defined Janus port to which the certificate is to be added. Can include wildcards. Non-SSL ports will not have trusted CA certificates added to them, since it is meaningless to have trusted CAs on a non-SSL port.</td></tr>

	<tr><th>filename</th>		<tr><th>filename</th>
	<td>The name of the file that contains the CA certificate.</td></tr>		<td>The name of the file that contains the CA certificate.</td></tr>

	<tr><th>procname</th>		<tr><th>procname</th>
	<td>The name of the procedure that contains the base64 encoded CA certificate. This certificate may have been generated by the <var class="product">Janus Network Security</var> certificate management application or by some other certificate management application, extracted from a browser's CA database, or downloaded from a certifying authority's web site.		<td>The name of the procedure that contains the base64 encoded CA certificate. This certificate may have been generated by the <var class="product">Janus Network Security</var> certificate management application or by some other certificate management application, extracted from a browser's CA database, or downloaded from a certifying authority's web site.
	</td></tr></table>		</td></tr></table>

	An example ADDCA command and system response follows:		An example <var>ADDCA</var> command and system response follows:

	<p class="code">JANUS ADDCA J2WEBS JANSSL MYSSL2.CERT		<p class="code">JANUS ADDCA J2WEBS JANSSL MYSSL2.CERT
Line 64:		Line 66:
	To view the list of trusted certificates and their contents, use the <var>[[JANUS DISPLAYCA]]</var> command. To view the number of received certificates signed by each trusted CA, use the <var>[[JANUS STATUSCA]]</var> command.		To view the list of trusted certificates and their contents, use the <var>[[JANUS DISPLAYCA]]</var> command. To view the number of received certificates signed by each trusted CA, use the <var>[[JANUS STATUSCA]]</var> command.

	For more information about certificates and certifying authorities, see the <var class="~~product~~">[~~http~~:~~//sirius-software.com/maint/download/jansslr~~.pdf Janus Network Security Reference Manual]</var>.		For more information about certificates and certifying authorities, see the <var class="book">[[Media:jansslrNew.pdf\|Janus Network Security Reference Manual]]</var>.

	==Adding SIRIUS-file certificates==		==Adding SIRIUS-file certificates==

	Although a server port is not likely to need to use the <var>JANUS ADDCA</var> command more than once, a client port may want to use it to add multiple certificates. As a convenience especially for a <var>CLSOCK</var> port connecting to an SSL server, Sirius pre-loads a set of standard certifying authorities' certificates to the <code>SIRIUS</code> procedure file (as of ''[[UL/SPF]]'' 7.3). ''[[Janus Sockets]]'' SSL client ports need to add the certificate(s) of the CA that signed the certificate of the server or servers to which the client will connect. (Janus does not allow a port to specify exceptions, that is, signed certificates that a port accepts without having the signing CA's certificate.)		Although a server port is not likely to need to use the <var>JANUS ADDCA</var> command more than once, a client port may want to use it to add multiple certificates. As a convenience especially for a <var>CLSOCK</var> port connecting to an SSL server, Sirius pre-loads a set of standard certifying authorities' certificates to the <code>SIRIUS</code> procedure file (as of ''[[UL/SPF]]'' 7.3). ''[[Janus Sockets]]'' SSL client ports need to add the certificate(s) of the CA that signed the certificate of the server or servers to which the client will connect. (Janus does not allow a port to specify exceptions, that is, signed certificates that a port accepts without having the signing CA's certificate.)

Line 76:		Line 77:
	The <var class="product">User Language</var> <code>ADDCA</code> utility lets you add some or all of these certificates at once to an SSL port. The utility is invoked at the command level via <code>INCLUDE</code>:		The <var class="product">User Language</var> <code>ADDCA</code> utility lets you add some or all of these certificates at once to an SSL port. The utility is invoked at the command level via <code>INCLUDE</code>:

	<p class="~~code~~">IN SIRIUS INCLUDE ADDCA ~~portname certificate~~		<p class="syntax">IN SIRIUS INCLUDE ADDCA <span class="term">portname certificate</span>
	<~~/p>~~
	<p class="~~caption~~">~~User Language ADDCA utility syntax~~
	</p>		</p>

	Where each parameter is positional and required:		Where each parameter is positional and required:

	<table ~~class="syntaxTable"~~>		<table>
	<tr><th>portname</th>		<tr><th>portname</th>
	<td>The defined Janus SSL port to which the certificate is to be added. The name can include wildcards. Non-SSL ports may '''not''' have trusted CA certificates added to them.</td></tr>		<td>The defined Janus SSL port to which the certificate is to be added. The name can include wildcards. Non-SSL ports may '''not''' have trusted CA certificates added to them.</td></tr>

	<tr><th>certificate</th>		<tr><th>certificate</th>
	<td>The name of the procedure that contains the base64 encoded CA certificate. This parameter may contain wildcards. To load all certificates in the <code>SIRIUS</code> file whose names begin with <code>CA_AOL</code>, you can use: <code>CA_AOL*</code>		<td>The name of the procedure that contains the base64 encoded CA certificate. This parameter may contain wildcards. To load all certificates in the <code>SIRIUS</code> file whose names begin with <code>CA_AOL</code>, you can use: <code>CA_AOL*</code>
Line 95:		Line 95:

	The utility internally runs a series of <var>ADDCA</var> commands like the following to load to <code>WEBBY</code> each certificate in file <code>SIRIUS</code> that matches the specified pattern:		The utility internally runs a series of <var>ADDCA</var> commands like the following to load to <code>WEBBY</code> each certificate in file <code>SIRIUS</code> that matches the specified pattern:
	<p class="code"> JANUS ADDCA WEBBY SIRIUS CA_ThawtePremiumServerCA		<p class="code">JANUS ADDCA WEBBY SIRIUS CA_ThawtePremiumServerCA
	JANUS ADDCA WEBBY SIRIUS CA_ThawteServerCA		JANUS ADDCA WEBBY SIRIUS CA_ThawteServerCA
	JANUS ADDCA WEBBY SIRIUS CA_ThawteTimestampingCA		JANUS ADDCA WEBBY SIRIUS CA_ThawteTimestampingCA
	JANUS ADDCA WEBBY SIRIUS CA_ThawteSGCCA		JANUS ADDCA WEBBY SIRIUS CA_ThawteSGCCA
	</p>		</p>
	<p>		<p class="note">'''Note:''' The CA certificates are stored as procedures with mixed-case names, which makes them much easier to scan visually, but a little more difficult to manipulate. </p>
	'''Note:''' The CA certificates are stored as procedures with mixed-case names, which makes them much easier to scan visually, but a little more difficult to manipulate. </p>

	For instance, if the above <~~code~~>INCLUDE</~~code~~> command is used, all the intended certificates are loaded, because the <code>CA_T</code> in uppercase matches the case of the corresponding characters in the certificate names. But if you want a more precise search and the name to be matched by the pattern includes mixed-case characters, the <code>INCLUDE</code> command must be bracketed with a set of <code>LOWER/UPPER</code> commands, as in:		For instance, if the above <var>INCLUDE</var> command is used, all the intended certificates are loaded, because the <code>CA_T</code> in uppercase matches the case of the corresponding characters in the certificate names. But if you want a more precise search and the name to be matched by the pattern includes mixed-case characters, the <code>INCLUDE</code> command must be bracketed with a set of <code>LOWER/UPPER</code> commands, as in:

	<p class="code">JANUS DEFINE MYSSLPORT * CLSOCK 10		<p class="code">JANUS DEFINE MYSSLPORT * CLSOCK 10

JAL at 18:43, 13 March 2013

2013-03-13T18:43:26Z

← Older revision		Revision as of 18:43, 13 March 2013
Line 13:		Line 13:
	<p class="syntax">JANUS ADDCA portname filename procname		<p class="syntax">JANUS ADDCA portname filename procname
	</p>		</p>


	Where each parameter is positional and required:		Where each parameter is positional and required:
Line 117:		Line 116:
	==See also==		==See also==
	<ul>		<ul>
	<li>[[~~List_of_Janus_commands\|~~Janus ~~command list~~]]		<li>[[List of Janus commands]]
	</ul>		</ul>

	[[Category:Janus commands\|JANUS ADDCA]]		[[Category:Janus commands\|JANUS ADDCA]]

JALWiccan: Automatically generated page update

2013-03-13T16:02:23Z

Automatically generated page update

← Older revision		Revision as of 16:02, 13 March 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:JANUS ADDCA}}		{{DISPLAYTITLE:JANUS ADDCA}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Add Certifying Authority to a port~~<section end="desc" />~~</span>		<span class="pageSubtitle">Add Certifying Authority to a port</span>

	For ports supporting encrypted communications, this command adds a "trusted" certifying authority's certificate (encrypted public key) to the port.		For ports supporting encrypted communications, this command adds a "trusted" certifying authority's certificate (encrypted public key) to the port.
Line 11:		Line 11:

	==Syntax==		==Syntax==
	<p class="syntax"~~><section begin="syntax" /~~>JANUS ADDCA portname filename procname		<p class="syntax">JANUS ADDCA portname filename procname
	~~<section end="syntax" />~~</p>		</p>

JAL at 18:53, 24 October 2012

2012-10-24T18:53:17Z

← Older revision		Revision as of 18:53, 24 October 2012
Line 11:		Line 11:

	==Syntax==		==Syntax==
	<p class="syntax"><section begin="syntax" /> JANUS ADDCA portname filename procname		<p class="syntax"><section begin="syntax" />JANUS ADDCA portname filename procname
	<section end="syntax" /></p>		<section end="syntax" /></p>

Line 28:		Line 28:
	An example ADDCA command and system response follows:		An example ADDCA command and system response follows:

	<p class="code"> JANUS ADDCA J2WEBS JANSSL MYSSL2.CERT		<p class="code">JANUS ADDCA J2WEBS JANSSL MYSSL2.CERT

	*** MSIR.0642: Added CA 'www.sirius-software.com' from file		*** MSIR.0642: Added CA 'www.sirius-software.com' from file
Line 77:		Line 77:
	The <var class="product">User Language</var> <code>ADDCA</code> utility lets you add some or all of these certificates at once to an SSL port. The utility is invoked at the command level via <code>INCLUDE</code>:		The <var class="product">User Language</var> <code>ADDCA</code> utility lets you add some or all of these certificates at once to an SSL port. The utility is invoked at the command level via <code>INCLUDE</code>:

	<p class="code">		<p class="code">IN SIRIUS INCLUDE ADDCA portname certificate
	IN SIRIUS INCLUDE ADDCA portname certificate
	</p>		</p>
	<p class="caption">User Language ADDCA utility syntax		<p class="caption">User Language ADDCA utility syntax
Line 102:		Line 101:
	JANUS ADDCA WEBBY SIRIUS CA_ThawteSGCCA		JANUS ADDCA WEBBY SIRIUS CA_ThawteSGCCA
	</p>		</p>
	<~~blockquote~~> The CA certificates are stored as procedures with mixed-case names, which makes them much easier to scan visually, but a little more difficult to manipulate.		<p>
			'''Note:''' The CA certificates are stored as procedures with mixed-case names, which makes them much easier to scan visually, but a little more difficult to manipulate. </p>

	For instance, if the above <code>INCLUDE</code> command is used, all the intended certificates are loaded, because the <code>CA_T</code> in uppercase matches the case of the corresponding characters in the certificate names. But if you want a more precise search and the name to be matched by the pattern includes mixed-case characters, the <code>INCLUDE</code> command must be bracketed with a set of <code>LOWER/UPPER</code> commands, as in:		For instance, if the above <code>INCLUDE</code> command is used, all the intended certificates are loaded, because the <code>CA_T</code> in uppercase matches the case of the corresponding characters in the certificate names. But if you want a more precise search and the name to be matched by the pattern includes mixed-case characters, the <code>INCLUDE</code> command must be bracketed with a set of <code>LOWER/UPPER</code> commands, as in:

	<p class="code"> JANUS DEFINE MYSSLPORT * CLSOCK 10		<p class="code">JANUS DEFINE MYSSLPORT * CLSOCK 10
	OPEN FILE SIRIUS		OPEN FILE SIRIUS
	*LOWER		*LOWER
	IN SIRIUS INCLUDE ADDCA MYSSLPORT America		IN SIRIUS INCLUDE ADDCA MYSSLPORT America
	*UPPER		*UPPER
	</p>		</p>

	The above sequence of commands would load the certificate named <code>CA_AmericaOnlineRootCertificationAuthority1</code> from file <code>SIRIUS</code>.</~~blockquote~~>		The above sequence of commands would load the certificate named <code>CA_AmericaOnlineRootCertificationAuthority1</code> from file <code>SIRIUS</code>.

			==See also==
			<ul>
			<li>[[List_of_Janus_commands\|Janus command list]]
			</ul>

	~~See: [[List_of_Janus_commands\|Janus command list]]~~
	[[Category:Janus commands\|JANUS ADDCA]]		[[Category:Janus commands\|JANUS ADDCA]]

JAL: /* Syntax */

2012-10-24T18:32:25Z

Syntax

← Older revision		Revision as of 18:32, 24 October 2012
Line 23:		Line 23:
	<td>The name of the file that contains the CA certificate.</td></tr>		<td>The name of the file that contains the CA certificate.</td></tr>
	<tr><th>procname</th>		<tr><th>procname</th>
	<td>The name of the procedure that contains the base64 encoded CA certificate. This certificate may have been generated by the ~~''[http://www.sirius-software.com/maint/download/jansslr.pdf~~ Janus Network Security~~]''~~ certificate management application or by some other certificate management application, extracted from a browser's CA database, or downloaded from a certifying authority's web site.		<td>The name of the procedure that contains the base64 encoded CA certificate. This certificate may have been generated by the <var class="product">Janus Network Security</var> certificate management application or by some other certificate management application, extracted from a browser's CA database, or downloaded from a certifying authority's web site.
	</td></tr></table>		</td></tr></table>

Line 65:		Line 65:
	To view the list of trusted certificates and their contents, use the <var>[[JANUS DISPLAYCA]]</var> command. To view the number of received certificates signed by each trusted CA, use the <var>[[JANUS STATUSCA]]</var> command.		To view the list of trusted certificates and their contents, use the <var>[[JANUS DISPLAYCA]]</var> command. To view the number of received certificates signed by each trusted CA, use the <var>[[JANUS STATUSCA]]</var> command.

	For more information about certificates and certifying authorities, see the [http://sirius-software.com/maint/download/jansslr.pdf Janus Network Security Reference Manual].		For more information about certificates and certifying authorities, see the <var class="product">[http://sirius-software.com/maint/download/jansslr.pdf Janus Network Security Reference Manual]</var>.

	==Adding SIRIUS-file certificates==		==Adding SIRIUS-file certificates==

JALWiccan: 1 revision

2012-10-24T18:23:13Z

1 revision

← Older revision	Revision as of 18:23, 24 October 2012
(No difference)