Lantronix IntelliBox-I/O IntelliBox-I/O - User Guide - Page 165

SSH, How Does SSH Authenticate?, What Does SSH Protect Against?, B: Networking and Security

Get Lantronix IntelliBox-I/O PDF manuals and user guides View all Lantronix IntelliBox-I/O manuals
Add to My Manuals
Save this manual to your list of manuals

Page 165 highlights

B: Networking and Security Certificate provides the receiver with a way to encode a reply. Digital Certificates come in 40-bit and 128-bit versions. There are two principal ways to obtain a Digital Certificate. It can be bought from a certificate vendor or a user can "self-sign" his or her own certificate. With the latter method, a user can use various tools, both open source and proprietary, to sign his or her own Digital Certificate, saving the time and expense of going through a certificate vendor. SSH Like SSL, Secure Shell (SSH) is a protocol that provides secure encrypted communications over unsecured TCP/IP networks such as the Internet. SSH allows for secure access to remote systems, eliminating potential security breaches such as spoofing and eavesdropping or hijacking of sessions. However, SSH differs significantly from SSL and, in fact, cannot communicate with SSL. The two are different protocols, though they have some overlap in how they accomplish similar goals. How Does SSH Authenticate? SSH authenticates using one or more of the following:  Password (the /etc/passwd or /etc/shadow in UNIX)  User public key (RSA or DSA, depending on the release)  Host based (.rhosts or /etc/hosts.equiv in SSH1 or public key in SSH2) What Does SSH Protect Against? SSH provides strong authentication and secure communications over insecure channels. It also provides secure connections that protect a network from attacks such as:  IP spoofing, where a remote host sends packets that pretend to originate from another, trusted host. SSH even protects against a spoofer on the local network that is pretending to be a router to the outside.  IP source routing, where a host pretends that an IP packet comes from another, trusted host.  DNS spoofing, where an attacker forges name server records.  Interception of cleartext passwords and other data by intermediate hosts.  Manipulation of data by people in control of intermediate hosts.  Attacks based on listening to authentication data and spoofed connections to the server. IntelliBox-I/O 2100 User Guide 165

  • 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
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
B: Networking and Security
IntelliBox-I/O 2100 User Guide
165
Certificate provides the receiver with a way to encode a reply. Digital Certificates come in
40-bit and 128-bit versions.
There are two principal ways to obtain a Digital Certificate. It can be bought from a
certificate vendor or a user can "self-sign" his or her own certificate. With the latter
method, a user can use various tools, both open source and proprietary, to sign his or her
own Digital Certificate, saving the time and expense of going through a certificate vendor.
SSH
Like SSL, Secure Shell (SSH) is a protocol that provides secure encrypted
communications over unsecured TCP/IP networks such as the Internet. SSH allows for
secure access to remote systems, eliminating potential security breaches such as
spoofing and eavesdropping or hijacking of sessions. However, SSH differs significantly
from SSL and, in fact, cannot communicate with SSL. The two are different protocols,
though they have some overlap in how they accomplish similar goals.
How Does SSH Authenticate?
SSH authenticates using one or more of the following:
Password (the /etc/passwd or /etc/shadow in UNIX)
User public key (RSA or DSA, depending on the release)
Host based (.rhosts or /etc/hosts.equiv in SSH1 or public key in SSH2)
What Does SSH Protect Against?
SSH provides strong authentication and secure communications over insecure channels.
It also provides secure connections that protect a network from attacks such as:
IP spoofing, where a remote host sends packets that pretend to originate from
another, trusted host. SSH even protects against a spoofer on the local network that
is pretending to be a router to the outside.
IP source routing, where a host pretends that an IP packet comes from another,
trusted host.
DNS spoofing, where an attacker forges name server records.
Interception of cleartext passwords and other data by intermediate hosts.
Manipulation of data by people in control of intermediate hosts.
Attacks based on listening to authentication data and spoofed connections to the
server.