JANUS CLSOCK - Revision history

JAL: /* Syntax */ typos

2016-12-06T20:25:52Z

Syntax: typos

← Older revision		Revision as of 20:25, 6 December 2016
Line 27:		Line 27:

	<tr><th>optional_parameters</th>		<tr><th>optional_parameters</th>
	<td>These parameters vary with the <var class="term">rule_type</var> value. See [[#JANUS CLSOCK rule types\|JANUS CLSOCK rule types]], below.		<td>These parameters vary with the <var class="term">rule_type</var> value. See [[#JANUS CLSOCK rule types\|JANUS CLSOCK rule types]], below. </td></tr>
	</table>		</table>

JAL: misc formatting

2016-12-06T20:23:57Z

misc formatting

← Older revision		Revision as of 20:23, 6 December 2016
Line 9:		Line 9:

	==Syntax==		==Syntax==
	<p class="syntax"><span class="literal">JANUS CLSOCK </span><span class="term">portname rule_type </span><span class="squareb">[</span><span class="term">~~optional parameters~~</span><span class="squareb">]</span>		<p class="syntax"><span class="literal">JANUS CLSOCK</span> <span class="term">portname rule_type </span><span class="squareb">[</span><span class="term">optional_parameters</span><span class="squareb">]</span>
	</p>		</p>

Line 19:		Line 19:

	<tr><th>rule_type</th>		<tr><th>rule_type</th>
	<td>The type of rule being specified for the port or ports. Valid <var class="term">~~rule_types~~</var> are:		<td>The type of rule being specified for the port or ports. Valid <var class="term">rule_type</var> are:
	<ul>		<ul>
	<li><var>DISALLOW</var> — Removes access permission.</li>		<li><var>DISALLOW</var> — Removes access permission.</li>
Line 25:		Line 25:
	</ul>		</ul>
	</td></tr>		</td></tr>

			<tr><th>optional_parameters</th>
			<td>These parameters vary with the <var class="term">rule_type</var> value. See [[#JANUS CLSOCK rule types\|JANUS CLSOCK rule types]], below.
	</table>		</table>

Line 52:		Line 55:
	</p>		</p>

	Here is a similar port definition deck enhanced to support SSL connections (the <code>SSL 0</code> option) to any remote port for any valid user (the ALLOW rules).		Here is a similar port definition deck enhanced to support SSL connections (the <code>SSL 0</code> option) to any remote port for any valid user (the <var>ALLOW</var> rules).
	The ADDCA rule at the end supports connections to ports that are secured with "unrecognized" SSL certificates, typically these would be self-signed certificates created with the Rocket JANSSL application.		The <var>ADDCA</var> rule at the end supports connections to ports that are secured with "unrecognized" SSL certificates, typically these would be self-signed certificates created with the Rocket JANSSL application.

	<p class="code">JANUS FORCE CLSOCK		<p class="code">JANUS FORCE CLSOCK
Line 126:		Line 129:
	<td>Indicates that a <var>$Sock_Conn</var> or <var>New</var> call or <var>SIRIUS DEBUG ON</var> command is allowed to access <var class="term">portname</var> if issued from an APSY subsystem with a name that matches the pattern <var class="term">subsysname</var>. <code>SUBSYS *</code> indicates that access is allowed by any subsystem. <code>SUBSYS ''</code> indicates that access is allowed only by a non-subsystem procedure or temporary request, or by an in-stream procedure.</td></tr>		<td>Indicates that a <var>$Sock_Conn</var> or <var>New</var> call or <var>SIRIUS DEBUG ON</var> command is allowed to access <var class="term">portname</var> if issued from an APSY subsystem with a name that matches the pattern <var class="term">subsysname</var>. <code>SUBSYS *</code> indicates that access is allowed by any subsystem. <code>SUBSYS ''</code> indicates that access is allowed only by a non-subsystem procedure or temporary request, or by an in-stream procedure.</td></tr>

	<tr><th><var>REMOTE</var> rmt_host rmt_portnum		<tr><th nowrap><var>REMOTE</var> rmt_host rmt_portnum
	<td>Access is allowed to <var class="term">portname</var> if the remote host and port number (<var>$Sock_Conn</var> or <var>New</var> method arguments or their defaults; or <var>SIRIUS DEBUG ON</var> command arguments for the Debugger Client address and port) match <var class="term">rmt_host</var> and <var class="term">rmt_portnum</var>, respectively.		<td>Access is allowed to <var class="term">portname</var> if the remote host and port number (<var>$Sock_Conn</var> or <var>New</var> method arguments or their defaults; or <var>SIRIUS DEBUG ON</var> command arguments for the Debugger Client address and port) match <var class="term">rmt_host</var> and <var class="term">rmt_portnum</var>, respectively.
	<p>		<p>
Line 235:		Line 238:
	<td>Indicates that a <var>$Sock_Conn</var> or <var>New</var> call or <var>SIRIUS DEBUG ON</var> command is not allowed to access <var class="term">portname</var> if issued from an APSY subsystem with a name that matches the pattern <var class="term">subsysname</var>. <code>SUBSYS *</code> indicates that access is allowed only by a non-subsystem procedure or temporary request, or by an in-stream procedure. <code>SUBSYS ''</code> indicates that access is allowed by any subsystem.</td></tr>		<td>Indicates that a <var>$Sock_Conn</var> or <var>New</var> call or <var>SIRIUS DEBUG ON</var> command is not allowed to access <var class="term">portname</var> if issued from an APSY subsystem with a name that matches the pattern <var class="term">subsysname</var>. <code>SUBSYS *</code> indicates that access is allowed only by a non-subsystem procedure or temporary request, or by an in-stream procedure. <code>SUBSYS ''</code> indicates that access is allowed by any subsystem.</td></tr>

	<tr><th><var>REMOTE</var> rmt_host rmt_portnum		<tr><th nowrap><var>REMOTE</var> rmt_host rmt_portnum
	<td>Indicates that access is not allowed to <var class="term">portname</var> if the remote host and port number (from <var>[[$Sock_Conn]]</var> or <var>Socket</var> class <var>[[New (Socket constructor)\|New]]</var> method arguments or their defaults; or <var>SIRIUS DEBUG ON</var> command arguments for the Debugger Client address and port) match <var class="term">rmt_host</var> and <var class="term">rmt_portnum</var>, respectively.		<td>Indicates that access is not allowed to <var class="term">portname</var> if the remote host and port number (from <var>[[$Sock_Conn]]</var> or <var>Socket</var> class <var>[[New (Socket constructor)\|New]]</var> method arguments or their defaults; or <var>SIRIUS DEBUG ON</var> command arguments for the Debugger Client address and port) match <var class="term">rmt_host</var> and <var class="term">rmt_portnum</var>, respectively.

JAL: /* JANUS CLSOCK ALLOW */ replace Sirius

2016-12-06T20:08:50Z

JANUS CLSOCK ALLOW: replace Sirius

← Older revision		Revision as of 20:08, 6 December 2016
Line 72:		Line 72:
	<li>A socket-connection $function <var>[[$Sock_Conn]]</var> or <var>Socket</var> class method <var>New</var> invocation to access the <var>CLSOCK</var> ports that match pattern <var class="term">portname</var>.		<li>A socket-connection $function <var>[[$Sock_Conn]]</var> or <var>Socket</var> class method <var>New</var> invocation to access the <var>CLSOCK</var> ports that match pattern <var class="term">portname</var>.

	<li>A <var class="product">~~Sirius~~ Debugger</var> user to access the <var>DEBUGGERCLIENT</var> ports that match pattern <var class="term">portname</var>.		<li>A <var class="product">TN3270 Debugger</var> user to access the <var>DEBUGGERCLIENT</var> ports that match pattern <var class="term">portname</var>.
	</ul>		</ul>

JAL: misc formatting

2016-09-22T20:02:29Z

misc formatting

Show changes

JAL: add IPV6 address format

2016-09-22T19:49:58Z

add IPV6 address format

Show changes

JAL: /* Syntax */

2013-08-21T20:13:32Z

Syntax

← Older revision		Revision as of 20:13, 21 August 2013
Line 26:		Line 26:
	</table>		</table>

	The <var>ALLOW</var> and <var>DISALLOW</var> rules are processed together, from most recent to oldest. The optional parameters allowed for the <var>JANUS CLSOCK</var> command depend on the <var class="term">rule_type</var> value. The rule types are shown below, followed by a section giving examples and showing the interaction of <var>JANUS CLSOCK</var> commands.		==Usage notes==
			<ul>
			<li>The <var>ALLOW</var> and <var>DISALLOW</var> rules are processed together, from most recent to oldest. The optional parameters allowed for the <var>JANUS CLSOCK</var> command depend on the <var class="term">rule_type</var> value. The rule types are shown below, followed by a section giving examples and showing the interaction of <var>JANUS CLSOCK</var> commands.

	~~Note that the~~ <var>JANUS CLSOCK</var> and <var>JANUS SRVSOCK</var> commands differ from the corresponding rules available with the <var>[[JANUS WEB]]</var> command in the following ways:		<li>The <var>JANUS CLSOCK</var> and <var>JANUS SRVSOCK</var> commands differ from the corresponding rules available with the <var>[[JANUS WEB]]</var> command in the following ways:

	<ul>		<ul>
Line 34:		Line 36:
	<li>The default access for <var>WEBSERV</var> non-SSL ports and <var>SRVSOCK</var> ports is <var>ALLOW</var>. The default access for <var>WEBSERV</var> SSL ports and <var>CLSOCK</var> and <var>DEBUGGERCLIENT</var> ports is <var>DISALLOW</var>.</li>		<li>The default access for <var>WEBSERV</var> non-SSL ports and <var>SRVSOCK</var> ports is <var>ALLOW</var>. The default access for <var>WEBSERV</var> SSL ports and <var>CLSOCK</var> and <var>DEBUGGERCLIENT</var> ports is <var>DISALLOW</var>.</li>
	<li><var>ALLOW</var> and <var>DISALLOW</var> are the only rule types for <var>JANUS CLSOCK</var> and <var>JANUS SRVSOCK</var>. There are a number of other rule types for <var>JANUS WEB</var>.</li>		<li><var>ALLOW</var> and <var>DISALLOW</var> are the only rule types for <var>JANUS CLSOCK</var> and <var>JANUS SRVSOCK</var>. There are a number of other rule types for <var>JANUS WEB</var>.</li>
			</ul>
	</ul>		</ul>

			==Examples==
	This is a simple port definition deck that allows connections to any remote site:		This is a simple port definition deck that allows connections to any remote site:

Alan at 16:29, 20 June 2013

2013-06-20T16:29:44Z

← Older revision		Revision as of 16:29, 20 June 2013
Line 45:		Line 45:
	</p>		</p>

	Here's a similar port definition deck enhanced to support SSL connections (the "SSL 0" ~~options~~) to any remote port for any valid user (the ALLOW rules). The ADDCA rule at the end supports connections to ports that are secured with "unrecognized" SSL certificates, typically these would be self-signed certificates created with the Rocket JANSSL application.		Here's a similar port definition deck enhanced to support SSL connections (the "SSL 0" option) to any remote port for any valid user (the ALLOW rules).
			The ADDCA rule at the end supports connections to ports that are secured with "unrecognized" SSL certificates, typically these would be self-signed certificates created with the Rocket JANSSL application.

	<p class="code">JANUS FORCE CLSOCK		<p class="code">JANUS FORCE CLSOCK

Alan at 16:20, 20 June 2013

2013-06-20T16:20:24Z

@@ Line 35: / Line 35: @@
 <li><var>ALLOW</var> and <var>DISALLOW</var> are the only rule types for <var>JANUS CLSOCK</var> and <var>JANUS SRVSOCK</var>. There are a number of other rule types for <var>JANUS WEB</var>.</li>
 </ul>
 ==JANUS CLSOCK rule types==

JAL: /* See also */

2013-03-13T18:38:32Z

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 CLSOCK}}		{{DISPLAYTITLE:JANUS CLSOCK}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Defines rules for a Janus socket client~~<section end="desc" />~~</span>		<span class="pageSubtitle">Defines rules for a Janus socket client</span>

	The <var>JANUS CLSOCK</var> command defines the rules for a <var class="product">[[Janus Sockets]]</var> client <var>CLSOCK</var> or <var>[[JANUS DEFINE#type\|DEBUGGERCLIENT]]</var> port. These rules control access to the port. ''System administrators always have access to a client port'', so no <var>CLSOCK</var> rules are required to provide socket access to these users.		The <var>JANUS CLSOCK</var> command defines the rules for a <var class="product">[[Janus Sockets]]</var> client <var>CLSOCK</var> or <var>[[JANUS DEFINE#type\|DEBUGGERCLIENT]]</var> port. These rules control access to the port. ''System administrators always have access to a client port'', so no <var>CLSOCK</var> rules are required to provide socket access to these users.

← Older revision		Revision as of 18:38, 13 March 2013
Line 269:		Line 269:
	==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 CLSOCK]]		[[Category:Janus commands\|JANUS CLSOCK]]