9
G&
GLIN
TM
Security
All Glink’s TCP/IP communications protocols support a choice of the Secure Socket Layer or Secure Shell
encryption and authentication protocols, giving you security on your Telnet, Rlogin, TN3270/TN3270E,
TN5250/TN5250E, TNVIP and Ggate connections to your legacy systems.
Secure Socket Layer
Glink can be configured to use the Secure Sockets Layer (SSL) included in Microsoft’s Secure Channel
(SChannel) security package on all supported Windows releases to provide secure communications.
When using Glink, privacy is ensured by use of encryption on all Secure Socket connections. Additionally,
X509 certificates from a trusted certificate authority can be used to authenticate the mainframe, the client or
both.
You set SSL by checking the ‘Use secure sockets’
radio button in the ‘Security’ pane of the Windows
sockets configuration dialog box. This gives you
encryption using default values.
In the advanced settings you can configure
authentication of the server, both by validating its
certificate and validating that the server name is
correct.
You can also choose to override the Automatic
selection of security protocol and key exchange
protocol.
Secure socket connections presume an SSL server. If your server system does not have SSL support you
can install a freeware package such as Stunnel to provide it.
Secure Shell
Glink can be configured to use the Secure Shell (SSH) included in the PuTTY Secure Shell freeware
package using the plink module. The PuTTY software is truly freeware and is distributed under the MIT
license, similar to BSD, and can therefore be included in Glink and other SSH clients.
When using Glink, privacy is ensured by use of encryption on all Secure Shell connections. You must have
an SSH logon name and password for the SSHD server to which you connect.
You set SSH by checking the ‘Use PuTTY SSHD’
radio button in the ‘Security’ pane of the Windows
sockets configuration dialog box.
In the advanced settings you must configure the
Secure Shell Daemon server address, and you can
configure your name and password. If you would
like to use Public Key authentication of your Glink
you can store your private key in the file system, in
which case the SSHD password can be used for
the passphrase needed to access it. You can also
choose to override the Automatic selection of
security protocol and key exchange protocol.
Secure Shell connections presume an SSH server.
(9 Seiten)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Kommentare zu diesen Handbüchern