![Scannex ip.buffer Скачать руководство пользователя страница 10](http://html1.mh-extra.com/html/scannex/ip-buffer/ip-buffer_manual_1206776010.webp)
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.4. Firmware
Firmware 2.90 and above is shipped as a single .BLF firmware file
“
IPBx.xx.xxx.blf
” where x.xx.xxx is the version number.
If cryptography is not permitted in your region Scannex can ship a special build of the
hardware that cannot run cryptography. The firmware file is identical, but the hardware
will prevent crypto code from running.
The web pages of the ip.buffer indicate whether cryptography is enabled:
•
IPBSSLx.xx.xxx
indicates that SSL/TLS/SSH cryptography is enabled.
•
IPBCFx.xx.xxx
indicates that cryptography is disabled.
Scannex have full export approval. See section 25.7
The cryptographic routines cannot be modified or updated by an end user.
6
Firmware 2.82 and earlier was shipped in two firmware files – an SSL and a CF version. However,
the ability to load SSL enabled firmware in the field still meant the hardware was “crypto capable”
from an import-restriction viewpoint.
Page 6
Scannex ip.buffer User Manual
© UK 2007-2021 Scannex Electronics Ltd. All rights reserved worldwide.
1.4. Firmware
Firmware 2.90 and above is shipped as a single .BLF firmware file
“
IPBx.xx.xxx.blf
” where x.xx.xxx is the version number.
If cryptography is not permitted in your region Scannex can ship a special build of the
hardware that cannot run cryptography. The firmware file is identical, but the hardware
will prevent crypto code from running.
The web pages of the ip.buffer indicate whether cryptography is enabled:
•
IPBSSLx.xx.xxx
indicates that SSL/TLS/SSH cryptography is enabled.
•
IPBCFx.xx.xxx
indicates that cryptography is disabled.
Scannex have full export approval. See section 25.7
The cryptographic routines cannot be modified or updated by an end user.
6
Firmware 2.82 and earlier was shipped in two firmware files – an SSL and a CF version. However,
the ability to load SSL enabled firmware in the field still meant the hardware was “crypto capable”
from an import-restriction viewpoint.
Page 6