Release notes | 10.5

1. Introduction

These release notes provide information about the latest features of iProtect, including required software versions and hardware installation and operating manuals.

2. System requirements

This chapter lists the required hardware and software for iProtect, including the licensing scheme of iProtect upgrades and other important information.

2.1 Supported servers

For installation and support of the iProtect server, the system requirements of Ubuntu server are followed. This may differ depending on system use and size.
In addition, the duration of support is determined by the lifespan of the hardware. This is issued by the hardware manufacturer and described as MTBF (Mean Time Between Failure).

2.2 Hardware specification

The hardware specification depends on many variables, so the required specification is customer specific.

Guide lines for 2500 card users and 250 readers and 5 concurrent users*.

Version	CPU	Ram	Disk
10.5	>= 2.0 Ghz dual core	16 GB	>= 500GB
Test system (small)	1.6 Ghz dual core	4 GB	100GB

For large systems (>1000 readers, >20 concurrent users), a minimum of 32GB internal memory and 8 cores is recommended. *

Depending of the use of images (keymaps, photo’s), the disk space should be checked.

Deploying iProtect on a virtual environment, the performance of the disk read/write can be depended to the other virtual machine deployed on the same hypervisor.

2.3 Software

The required operating system version for iProtect:

iProtect version	Ubuntu lts	iProtect-setup	Servbox	Internet connection required
10.5	24.04	= > 3.1.0	= >10.03.01	Yes, for installation and updates

For iProtect 10.05 and Ubuntu 24.04, there is a TKH repository with all needed files for installing and maintaining the setup files.

The operating system can be downloaded from Ubuntu's default repository.

It is highly recommended to ensure that iProtect is connected to the internet during installation. Permanent access to the internet is of course possible, but temporary internet access for updating the security packages is also possible.

On request there is an option to install iProtect without an internet connection but is not recommended.

2.4 Update policy

TKH security works non-stop to improve its products and their safety.
From iProtect version 10.5, the software version from which you update and the software version to which you update must be taken into account.

2.4.1 Which iProtect version supports which Pluto RootFS

To ensure a reliable and secure system, the following software versions are required:

iProtect version	Ubuntu lts	rootFS
10.1 or lower	16.04	V5-68a
10.2 - 10.4	20.04	V6.11.14 - V7-xx
10.5	24.04	V6.11.14 - V7-xx

Although RootFS v5-68a is still supported by iProtect 10.2 and 10.3, this will no longer be the case when iProtect 10.4 or higher is used.

Before updating to iProtect version 10.5, the system should first be updated to version 10.3 or higher with rootFS version 6.x.

Before updating to iProtect version 10.5, controllers should be running RootFS v6.11.14 or higher.

2.5 Software and firmware

Software versions of the connected hardware are managed from iProtect by default.
Below you will find an overview of the most used hardware and the minimum version that are installed (provisioned) when updating iProtect.

Hardware / Device	Software / Firmware (minimum)
Pluto (RootFS)	6.12.03
Reader manager	6.x
Orion	1.5.34
iX-serie Reader firmware	3.x
RIO firmware	1.2.50 / 2.16.0
TANLock	1.0.0

Release notes of the software/firmware are available on request.

If software/firmware versions have a lower number than shown in the table above, it will be automatically updated. Although this time is kept as short as possible, the customer may be inconvenienced for a short time.

When updating iProtect, all network controllers will be updated automatically to the latest RootFS version. This update will be processed in the background and will take approximately 10 - minutes (depending on network speed).

During the preparation of the update, the customer will not experience any inconvenience.

When the update is complete, the system administrator must reboot the controller. Booting up the controller will take approximately 2 minutes (depending on network speed). During this time, the customer may experience problems opening the door.

2.6 Encrypted JDBC connection

iProtect 10.5 requires an encrypted (SSL mode) jdbc connection.

Required .Jar files for iProtect v10.03.xx and higher:

java-library-xx.x.x.jar
keyprocessor-jdbc-xx.x.x.jar
log4j-api-x.x.xx.jar
log4j-core-x.x.xx.jar
icu4j-73.1.jar
tyrus-standalone-client-x.xx.jar

2.6.1 API documentation available (on request)

If desired, new API documentation is available:

JDBC over SSL
iProtect XML API v2.16

Please contact TKH-Security for these API documents.

TKH security tries to keep the links working at all times, but cannot guarantee this in case of an upgrade. When connecting third-party systems to Protect, it is strongly recommended to test for proper operation with a preset test system before upgrading.

2.6 License

When a major version number changes, it should be taken into account in advance that a new license is necessary. Please contact TKH Security service department or your account manager for this.

From version	To version	New license needed
10.3.x	10.4.x	Yes
10.4.x	10.5.x	Yes
10.5.x	10.5.x	No

2.7 Browser support

All tests are done with default browser settings, if some functionalities require changes to the settings, this will be mentioned in the specific manual. The following browsers are supported in iProtect:

Browser	Version
Google Chrome	132.0
Mozilla Firefox	134.0
Microsoft Edge	132.0

Microsoft internet explorer (IE) is not supported anymore.

3. End of support

Sirius 1 support in combination with Reader manager version 6
SimonsVoss SI2
Traka 32 support

3.1 Pre-announcement

3.1.1 Network controller

Polyx Network controller: End of life: 31-12-2025
Apollo 1: End of life: 31-12-2025
iPU-8: End of life per: 31-12-2025

3.1.2 Support of INVR / License plate recognition on Polyx and IPU-8

iProtect 10.4 will be the last version which supports an iNVR Node on a iPU-8 or Polyx controller. If this situation occurs, the advise is to move the INVR node to a local server line.

3.2 Revised advance notice

Making use of the hta-tool can entail security risks. That was the reason we wanted to deprecate this.
Since many customers are still using this tool, an option has been added to continue using this hta tool. This usage is disabled by default.

The following option has been added to the dialog:

Installation | Settings | System parameters, tab: Other, “HTA enable”.

4. iProtect server and application

In every new version of iProtect, there will be product improvements (bug fixes). The section below lists changes or newly added fucntionality compared to iProtect 10.4.

IPROTECT Access version 10.5 is similar as a basis to the last released version 10.4.

4.1 Free unique text field

In iProtect version 10.5 it is possible to use a unique free (pager) number (range). If the number already exists, you will get an error message.

button (next free number)
manual entry

IPROTECT - Release notes 10.5

Table of contents