Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
14.3. Server Certificate
For SSL/TLS server operation the ip.buffer requires at least one certificate to allow the
client to identify the ip.buffer. When shipped the ip.buffer includes the following
certificates:
Scannex Root CA certificate
Scannex ip.buffer certificate
Default ip.buffer certificate for 192.168.0.235
The client will check whether the last certificate matches the address used to access the
ip.buffer. If they mismatch the client normally shows an error. So that you can customise
the certificate you can either generate a certificate or upload one you create on a PC.
14.3.1. Generate
http://192.168.0.235/setup/makecer.shtm
This option will generate both a TLS/SSL PKI X509 certificate and a corresponding SSH key
RSA Key Size
Choose the RSA key size for the certificate
[1024-bit]
Hostname
The name for the certificate. The client checks that this
hostname matches the address used to access the ip.buffer. Can
be either an IP address (e.g. 192.168.0.235) or a name (e.g.
ipbuffer.scannex.co.uk).
It defaults to the address you used in the browser and should not
require changing.
Organisation Name
Optional
Organisation Unit
Optional
City
Optional
State or Province
Optional
Country
A two character certificate identifier. e.g. “US” or “GB”
[GB]
Optional
Validity
From
The time the certificate starts (defaults to midnight today)
To
The time the certificate expires
3
The SSH key is actually the RSA key that is contained within the X509 certificate.
4
512-bit keys are not accepted by modern browsers. 2048-bit keys can take 5 minutes to create!
Page 118
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
14.3. Server Certificate
For SSL/TLS server operation the ip.buffer requires at least one certificate to allow the
client to identify the ip.buffer. When shipped the ip.buffer includes the following
certificates:
Scannex Root CA certificate
Scannex ip.buffer certificate
Default ip.buffer certificate for 192.168.0.235
The client will check whether the last certificate matches the address used to access the
ip.buffer. If they mismatch the client normally shows an error. So that you can customise
the certificate you can either generate a certificate or upload one you create on a PC.
14.3.1. Generate
http://192.168.0.235/setup/makecer.shtm
This option will generate both a TLS/SSL PKI X509 certificate and a corresponding SSH key
RSA Key Size
Choose the RSA key size for the certificate
[1024-bit]
Hostname
The name for the certificate. The client checks that this
hostname matches the address used to access the ip.buffer. Can
be either an IP address (e.g. 192.168.0.235) or a name (e.g.
ipbuffer.scannex.co.uk).
It defaults to the address you used in the browser and should not
require changing.
Organisation Name
Optional
Organisation Unit
Optional
City
Optional
State or Province
Optional
Country
A two character certificate identifier. e.g. “US” or “GB”
[GB]
Optional
Validity
From
The time the certificate starts (defaults to midnight today)
To
The time the certificate expires
3
The SSH key is actually the RSA key that is contained within the X509 certificate.
4
512-bit keys are not accepted by modern browsers. 2048-bit keys can take 5 minutes to create!
Page 118