Lantronix Spider Lantronix Spider / SpiderDuo - User Guide - Page 87

Certificate, Services > Certificate

Get Lantronix Spider PDF manuals and user guides View all Lantronix Spider manuals
Add to My Manuals
Save this manual to your list of manuals

Page 87 highlights

9: Services Certificate The Spider device uses the Secure Socket Layer (SSL) protocol for any encrypted network traffic between itself and a connected client. During the connection establishment the Spider device has to expose its identity to a client using a cryptographic certificate. Upon leaving the factory this certificate and the underlying secret key is the same for all Spider devices and will not match the network configuration where it is installed. The certificate's underlying secret key is also used for securing the SSL handshake. Leaving the default certificate unmodified is all right in most circumstances and is necessary only if the network facility is vulnerable to man-in-the-middle attack. It is possible to generate and install a new base64 x.509 certificate that is unique for a particular Spider device. The Spider device is able to generate a new cryptographic key and the associated Certificate Signing Request (CSR) that needs to be certified by a certification authority (CA). To create and install an SSL certificate, perform the following steps. 1. Click Services > Certificate. The Certificate Signing Request page displays. Figure 9-4 Certificate Signing Request Page 2. Modify the following fields. Field Common name Organizational unit Organization Locality/City Description The network name of the Spider device once it is installed in the user's network (usually the fully qualified domain name). It is identical to the name that is used to access the Spider device with a web browser without the prefix http://. In case the name given here and the actual network name differ, the browser will pop up a security warning when the Spider device is accessed using HTTPS. This field specifies to the department within an organization to which the Spider device belongs. The name of the organization to which the Spider device belongs. The city where the organization is located. Spider™ and SpiderDuo® KVM-over-IP Device User Guide 87

  • 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
9: Services
Spider™ and SpiderDuo® KVM-over-IP Device User Guide
87
Certificate
The Spider device uses the Secure Socket Layer (SSL) protocol for any encrypted network traffic
between itself and a connected client. During the connection establishment the Spider device has
to expose its identity to a client using a cryptographic certificate. Upon leaving the factory this
certificate and the underlying secret key is the same for all Spider devices and will not match the
network configuration where it is installed. The certificate’s underlying secret key is also used for
securing the SSL handshake. Leaving the default certificate unmodified is all right in most
circumstances and is necessary only if the network facility is vulnerable to man-in-the-middle
attack.
It is possible to generate and install a new base64 x.509 certificate that is unique for a particular
Spider device. The Spider device is able to generate a new cryptographic key and the associated
Certificate Signing Request (CSR) that needs to be certified by a certification authority (CA).
To create and install an SSL certificate, perform the following steps.
1.
Click
Services > Certificate
.
The Certificate Signing Request page displays.
Figure 9-4
Certificate Signing Request Page
2.
Modify the following fields.
Field
Description
Common name
The network name of the Spider device once it is installed in the user’s
network (usually the fully qualified domain name). It is identical to the name
that is used to access the Spider device with a web browser without the
prefix http://. In case the name given here and the actual network name
differ, the browser will pop up a security warning when the Spider device is
accessed using HTTPS.
Organizational unit
This field specifies to the department within an organization to which the
Spider device belongs.
Organization
The name of the organization to which the Spider device belongs.
Locality/City
The city where the organization is located.