For more information, see the following topics:
•
Interfaces for Security Devices
•
Understanding Management Access
Telnet allows you to connect to the services gateway and access the CLI to execute
commands from a remote system. The Telnet CLI connections are not encrypted and
therefore can be intercepted.
NOTE:
Telnet access to the root user is prohibited. You must use more secure
methods, such as SSH, to log in as
root
.
SSH provides the following features:
•
Allows you to connect to the device and access the CLI to execute commands from a
remote system
•
Encrypts traffic so that it cannot be intercepted (unlike Telnet)
•
Can be configured so that connections are authenticated by a digital certificate
•
Uses public–private key technology for both connection and authentication
The SSH client software must be installed on the machine where the client application
runs. If the SSH private key is encrypted (for greater security), the SSH client must be
able to access the passphrase used to decrypt the key.
For information about obtaining SSH software, see
and
.
If you are using a Junos XML protocol server to configure and monitor devices, you can
activate cleartext access on the device to allow unencrypted text to be sent directly over
a Transmission Control Protocol (TCP) connection without using any additional protocol
(such as SSH, Secure Sockets Layer [SSL], or Telnet). For more information about the
Junos XML management protocol, see the
NETCONF XML Management Protocol Guide
If the device is operating in a Common Criteria environment, see the
for Junos OS Public Sector Certifications
.
Related
Documentation
Connecting an SRX220 Services Gateway to the CLI Locally on page 83
•
•
Connecting an SRX220 Services Gateway to the CLI Remotely on page 85
•
Performing Initial Software Configuration on the SRX220 Services Gateway Using the
CLI on page 92
•
SRX220 Services Gateway Secure Web Access Overview on page 82
Copyright © 2016, Juniper Networks, Inc.
80
SRX220 Services Gateway Hardware Guide for H Model Numbers
