Juniper SRX210 Series Manual page 146

SRX210 Services Gateway Hardware
Related
Documentation
128
NOTE: Telnet access to the root user is prohibited. You must use more secure
methods, such as SSH, to log in as
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
.
http://www.openssh.com
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 Line Protocol (TCP) connection without using any additional protocol
(such as SSH, SSL, or Telnet). For more information about the Junos XML management
protocol, see the
NETCONF XML Management Protocol Guide
NOTE: Information sent in cleartext is not encrypted and therefore can be
intercepted.
If the device is operating in a Common Criteria environment, see the Secure Configuration
Guide for Common Criteria and Junos-FIPS.
Connecting to the SRX210 Services Gateway Setup Wizard on page 117
Connecting an SRX210 Services Gateway to the CLI Locally on page 118
Connecting an SRX210 Services Gateway to the CLI Remotely on page 120
Performing Initial Software Configuration on the SRX210 Services Gateway Using the
Setup Wizard
Performing Initial Software Configuration on the SRX210 Services Gateway Using the
CLI on page 129
SRX210 Services Gateway Secure Web Access Overview on page 137
.
root
http://www.ssh.com and
.
Copyright © 2012, Juniper Networks, Inc.