To Next Page

To Previous Page

114 • Configuring and Running SSH2 HP NonStop SSH Reference Manual

The pre-selected service or window ('srvc1' and '#win1' in the examples above) must exist in the STN configuration.

STN services and windows can be added with STNCOM, using the ADD SERVICE and ADD WINDOW commands.

Please refer to the "STNCOM Commands" section for further details.

Forcing TACL Access via Server-side Configuration

Usually a remote user can select if the ssh client gets access to an OSS shell or a TACL. In case the user executes a

SHELL request e.g.:

ssh usr@host

and the terminal type is TN6530, then a TACL is created. Also, if the user executes a SUBSYSTEM request with

subsystem name tacl, e.g.:

ssh –s usr@host tacl

then a TACL is started. If the user executes a SHELL request like

ssh usr@host

and the terminal type is not TN6530, then a shell is started. In case the user starts an EXEC request specifying a

command like in:

ssh usr@host ls –l

then the command is executed in a shell. If a TACL command should be executed, then the gtacl shell command can be

used, e.g.

ssh usr@host gtacl -c fileinfo

or the command tacl with options –c like

ssh usr@host tacl –c fileinfo

A program can be started in the TACL environment using option –p, e.g.:

ssh usr@host tacl –p fup

A way to force a user to connect to a TACL is to define an STN service and configure the SSH USER record to use this

service.

Assuming a service TACL1 is defined via STNCOM like:

ADD SERVICE TACL1, TYPE DYNAMIC, PROG $system.system.tacl, LOGON REQ

And the SSH user is configured using SSHCOM commands:

ALTER USER usr, SHELL-PROGRAM *MENU* TACL1 FORCE

Then both SHELL and EXEC requests, independent of the terminal type will start a TACL.

If the user was successfully authenticated via a different ssh authentication method than none, i.e. the USER attribute

ALLOWED-AUTHENTICATIONs was not set to (none), the TACL starts already logged on as user usr because the

service was added with “LOGON REQ”.

Using TELSERV as Service Provider

6530 shell channels can also be forwarded to a TELSERV process. This enables a fast and easy migration of an existing

complex TELSERV environment to SSH, such as an environment with static windows. To forward 6530 shell requests

to TELSERV, specify the CI-PROGRAM as follows:

>SSHCOM <ssh2 process name>

%ALTER USER telnetuser, CI-PROGRAM telnet

HP NonStop SSH 544701-014 User Manual

Questions and Answers: