Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

SSH Tectia

Component Terminology

The following terms are used throughout the documentation.

client computer

The computer from which the Secure Shell connection is initiated.

Connection Broker

The Connection Broker is a component included in SSH Tectia Client and SSH Tectia ConnectSecure, as well as SSH Tectia Server for IBM z/OS client tools. Connection Broker handles all cryptographic operations and authentication-related tasks.

file transfer GUI

SSH Tectia Client and ConnectSecure include a separate graphical user interface (GUI) for handling and performing file tranfers.

host key pair

A public-key pair used to identify a Secure Shell server. The private key file is accessible only to the server. The public key file is distributed to users connecting to the server.

remote host

Refers to the other party of the connection, client computer or server computer, depending on the viewpoint.

Secure Shell client

A client-side application that uses the Secure Shell version 2 protocol, for example sshg3, sftpg3, or scpg3 of SSH Tectia Client.

Secure Shell server

A server-side application that uses the Secure Shell version 2 protocol.

server computer

The computer on which the Secure Shell service is running and to which the Secure Shell client connects.

SFTP server

A server-side application that provides a secure file transfer service as a subsystem of the Secure Shell server.

SSH Tectia Client

A software component installed on a workstation. SSH Tectia Client provides secure interactive file transfer and terminal client functionality for remote users and system administrators to access and manage servers running SSH Tectia Server or other applications using the Secure Shell protocol. It also supports (non-transparent) static tunneling, and as an optional feature on Windows, transparent TCP tunneling.

SSH Tectia client/server solution

The SSH Tectia client/server solution consists of SSH Tectia Client, SSH Tectia ConnectSecure, SSH Tectia Server, and SSH Tectia Server for IBM z/OS.

SSH Tectia Configuration GUI

SSH Tectia Client and ConnectSecure have a graphical user interface (GUI) for configuring the Connection Broker settings which control the behaviour of the SSH Tectia product.

SSH Tectia ConnectSecure

A software component installed on a server host, but it acts as a Secure Shell client. SSH Tectia ConnectSecure is designed for FTP replacement and it provides FTP-SFTP conversion, transparent FTP tunneling, transparent TCP tunneling, and enhanced file transfer services. SSH Tectia ConnectSecure is capable of connecting to any standard Secure Shell server.

SSH Tectia SFTP API

SSH Tectia ConnectSecure includes separate application programming interfaces (API) for C and Java. The APIs can be used by developers who develop secure file transfer applications or integrate SSH Tectia products into other systems.

SSH Tectia Server

SSH Tectia Server is a server-side component where Secure Shell clients connect to. There are three versions of the SSH Tectia Server product available: SSH Tectia Server for Linux, Unix and Windows platforms, SSH Tectia Server for Linux on IBM System z, and SSH Tectia Server for IBM z/OS.

SSH Tectia Server for Linux on IBM System z

SSH Tectia Server for Linux on IBM System z provides Secure Shell connections on Linux running on IBM System z platforms.

SSH Tectia Server for IBM z/OS

SSH Tectia Server for IBM z/OS provides normal Secure Shell connections and supports the enhanced file transfer (EFT) features and transparent TCP tunneling on IBM mainframes.

transparent FTP tunneling

An FTP connection transparently encrypted and secured by a Secure Shell tunnel.

transparent TCP tunneling

A TCP application connection transparently encrypted and secured by a Secure Shell tunnel.

tunneled application

A TCP application secured by a Secure Shell connection.

user key pair

A public-key pair used to identify a Secure Shell user. The private key file is accessible only to the user. The public key file is copied to the servers the user wants to connect to.

===AUTO_SCHEMA_MARKUP===