Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
Security Certificate Global Options
Verify Servers
“
Ignore (allow any certificate)
” – will allow any
certificate. The fingerprint of any servers the ip.buffer
connects to will appear in the “Recent Fingerprints” list.
“
Fingerprint must be approved
” – only servers that have
certificates that match the approved fingerprint list can
be connected to. Any others will result in an error.
[Ignore (allow any certificate)]
Verify Date
“
Ignore
” – the validity date of the certificate is not checked.
“
Must be in date
” – the certificate date is checked. If out of
date then an error is reported and the connection closed.
[Ignore]
Verify Name
“
Ignore
” – does not check the certificate name.
“
Address and CN must match
” – the address entered in the
ip.buffer must match the certificate CN (Common Name)
field
[Ignore]
Verify Clients
“
Ignore (allow any certificate)
” – will allow any
certificate. The fingerprint of any clients that connect to
the ip.buffer will appear in the “Recent Fingerprints” list.
“
Fingerprint must be approved
” – only clients that have
certificates that match the approved fingerprint list can
be connected to. Any others will be rejected. In addition,
if a client does not provide a certificate then the client
will be rejected. The client certificate date and name are
also checked according to the above two rules.
[Ignore (allow any certificate)]
A link at the bottom of the Certificates page allows “Advanced security options...”
43
Source certificates (client & server) are not checked. Some devices have very weakly protected
private keys and can be compromised. For this reason, only destination and pass-thru certificates
are validated.
44
Only explicit common names are currently supported (e.g. “collect.scannex.com”). Wildcard
common names are not supported (e.g. “*.scannex.com”)
Page 46
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
Security Certificate Global Options
Verify Servers
“
Ignore (allow any certificate)
” – will allow any
certificate. The fingerprint of any servers the ip.buffer
connects to will appear in the “Recent Fingerprints” list.
“
Fingerprint must be approved
” – only servers that have
certificates that match the approved fingerprint list can
be connected to. Any others will result in an error.
[Ignore (allow any certificate)]
Verify Date
“
Ignore
” – the validity date of the certificate is not checked.
“
Must be in date
” – the certificate date is checked. If out of
date then an error is reported and the connection closed.
[Ignore]
Verify Name
“
Ignore
” – does not check the certificate name.
“
Address and CN must match
” – the address entered in the
ip.buffer must match the certificate CN (Common Name)
field
[Ignore]
Verify Clients
“
Ignore (allow any certificate)
” – will allow any
certificate. The fingerprint of any clients that connect to
the ip.buffer will appear in the “Recent Fingerprints” list.
“
Fingerprint must be approved
” – only clients that have
certificates that match the approved fingerprint list can
be connected to. Any others will be rejected. In addition,
if a client does not provide a certificate then the client
will be rejected. The client certificate date and name are
also checked according to the above two rules.
[Ignore (allow any certificate)]
A link at the bottom of the Certificates page allows “Advanced security options...”
43
Source certificates (client & server) are not checked. Some devices have very weakly protected
private keys and can be compromised. For this reason, only destination and pass-thru certificates
are validated.
44
Only explicit common names are currently supported (e.g. “collect.scannex.com”). Wildcard
common names are not supported (e.g. “*.scannex.com”)
Page 46
![Lambrecht Ser[LOG] Operator'S Manual preview](http://thumbs.mh-extra.com/thumbs/lambrecht/ser-log/ser-log_operators-manual_3390951-001.webp)
