Digi ConnectPort X4 User's Guide download pdf (Page 234)

Administration from the web interface

234

Behavior of SSH/SSL private keys on Digi devices

Digi devices generate their SSH/SSL self-signed private keys automatically. While this automatic

generation is convenient for device users, as they are not required perform any actions regarding

the private keys, it presents some security loopholes.

 With self-signed private keys, you must establish trust in a secure environment. That is,

if you cannot guarantee that the environment is secure, you must pull the private keys

off the Digi device.

 You must know about the certificate before you connect, as opposed to third-party

signed certificates, where you only need the third-party certificate.

 The length of Digi’s self-signed private keys is 1024 bits. While this length this is

adequate for 99.9% of all applications, some people or applications prefer a shorter or

longer key.

Using TFTP to load and store certificate information

Using TFTP, you can load and store PEM-formatted certificates into the certificate and private key

management tables.

Using HTTP/HTTPS to transfer certificate and key data

On the web, you can use HTTP or HTTPS to transfer certificate and private key data.

Data retained after factory reset

When a Digi device is reset to factory defaults, any certificates and private key data loaded onto it

are retained.

Certificate management settings

There are separate pages of settings for the certificate databases and key management for

certificates and key data for the different types of security implementations.

1 2 ... 229 230 231 232 233 234 235 236 237 238 239 ... 270 271

No comments

Digi ConnectPort X4 User's Guide Page 234