Dell PowerConnect J-SRX240 Hardware Guide - Page 89

Understanding Management Access, JUNOS Software Security Configuration Guide

Page 89 highlights

Chapter 14: Performing Initial Software Configuration on the J-SRX240 Services Gateway • JUNOS Software Security Configuration Guide Understanding Management Access Telnet allows you to connect to the services gateway and access the CLI to execute commands from a remote system. 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 http://www.ssh.com and http://www.openssh.com. If you are using a JUNOScript 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 JUNOScript application programming interface (API), see the JUNOS Software JUNOScript API 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. Related Topics • Connecting the J-SRX240 Services Gateway to the J-Web Interface on page 63 • Connecting the J-SRX240 Services Gateway to the CLI on page 66 • Performing Initial Software Configuration on the J-SRX240 Services Gateway Using the CLI on page 74 • Performing Initial Software Configuration on the J-SRX240 Services Gateway Using the J-Web Interface on page 76 • J-SRX240 Services Gateway Secure Web Access Overview on page 82 73

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

JUNOS Software Security Configuration Guide
Understanding Management Access
Telnet allows you to connect to the services gateway and access the CLI to execute
commands from a remote system. 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 JUNOScript 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 JUNOScript application
programming interface (API), see the
JUNOS Software JUNOScript API 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
.
Related Topics
Connecting the J-SRX240 Services Gateway to the J-Web Interface on page 63
Connecting the J-SRX240 Services Gateway to the CLI on page 66
Performing Initial Software Configuration on the J-SRX240 Services Gateway Using
the CLI on page 74
Performing Initial Software Configuration on the J-SRX240 Services Gateway Using
the J-Web Interface on page 76
J-SRX240 Services Gateway Secure Web Access Overview on page 82
73
Chapter 14: Performing Initial Software Configuration on the J-SRX240 Services Gateway