TOSIBOX® Central Lock Software Release Notes
Contact us Subscribe

Central Lock Software Release Notes

v2.3.0 – release date 2017-12-15 (Central Lock and Virtual Central Lock)

  • Added SoftKey support
  • New device icons for different client types in web UI
  • Fix for an issue where adding an incomplete static route or another default route caused system malfunction
  • Fix for an issue where certain parts of the web UI didn’t work with Mozilla Firefox
  • Reliability improvements
  • Includes all v2.1.0 – v2.2.0 changes also for Central Lock
  • Notice for Central Lock users updating from v1.4.0: This version replaces earlier IP/MAC filter functionality with Access Groups. During the update, the system will migrate most of the earlier IP/MAC filter rules to Access Groups but there can be certain configurations that cannot be fully migrated nor are supported with Access Groups, e.g. rules affecting communication between Layer 2 connections within the same LAN. Please note this before installing the update and please verify the you have correct settings in Access Groups after the update and make adjustments if required.

v2.2.0 – release date 2017-07-05 (Virtual Central Lock only)

  • Master Key can now be matched remotely with the Virtual Central Lock (read more)
  • Access groups can now be enabled/disabled
  • Mobile Clients inherit now their initial access rights from the Key that was used to create them
  • Added warnings when deleting WAN or LAN interfaces
  • Fix for an issue where Mobile Clients could not connect if they didn’t belong to any access group
  • Fix for an issue where iOS Mobile Client could not connect
  • Scan for LAN devices function fixed

v2.1.1 – release date 2017-05-29 (Virtual Central Lock only)

  • Fix for a mouse issue on VMWare ESXi
  • Fix for an issue where the network interface ordering might have changed after adding new network adapters to the virtual machine

v2.1.0 – release date 2017-03-31 (Virtual Central Lock only)

  • First SW release for the Virtual Central Lock
  • Support for defining access rights with access groups
  • Support for virtual LANs
  • New, streamlined web user interface for Central Lock and Virtual Central Lock
  • Support for global Lock names
  • The Lock’s name is now shown and can be changed in the web UI
  • The time zone can be configured
  • Added support for NTP (Network Time Protocol) server
  • New production units now show the end-user license agreement when the admin logs in for the first time
  • Improved reliability of refreshing status information in the web UI
  • Gateway option is no longer shown for LAN and VLAN interfaces
  • Mitigation for a security issue with VPN connections using Blowfish cipher: TBSA-016-301 (CVE-2016-6329)
    • The VPN data channel key is renegotiated much more frequently when Blowfish is used
    • AES-128-CBC is now the default VPN cipher for new Lock 100 production units
    • Lock-to-Lock and Lock-to-Central Lock connections now honor the VPN cipher setting of the main Lock or Central Lock
  • WAN port IP address is now shown on web UI also when using DHCP

v1.4.0 – release date 2015-06-25

  • Support for iOS Mobile Clients
  • Key-specific IP/MAC filter: access to LAN network devices can now be defined separately for each Key
  • Option to add exceptions for restricted Internet access (Industry settings ->Prevent Internet access from LAN …)
  • Network device list is now sorted alphabetically in the web UI
  • Available software updates are now announced in the web UI
  • Support for choosing the preferred VPN data encryption cipher (AES or Blowfish)
  • Improved performance with large number of VPN clients
  • Improved connection establishment time for Layer 3 Key connections
  • Lock’s friendly name is now visible in the alert email subject
  • Connection type is now Layer 3 for all new Sub Keys and Backup Keys
  • New production units have now 3072 bit RSA keys
  • “Wired” text is now shown also for devices in ports LAN2-4
  • Fix for an issue where connection alerts were sent even though the connection was restored before timeout
  • Fix for an issue where the connection names could sometimes get lost when saving Tosibox devices page
  • Fix for an issue with network device list when L3 Locks had a large number of devices

v1.3.2 – release date 2014-11-28

  • Fix for an issue where the Central Lock might not reconnect to Internet after a network problem

v1.3.1 – release date 2014-11-21

  • Fix for a web UI issue that affected new produced units

v1.3.0 – release date 2014-11-12

  • Log data can now be exported in CSV format
  • Log events are now generated for web UI login/logout
  • Email alerts can be triggered also from system failures (e.g. failing hard drives)
  • Connection alerts have now a configurable timeout to prevent alerts from short disconnects
  • SW updates can now be installed from the web UI
  • Security updates are installed automatically daily
  • Initial support for AES ciphers, with AES-256-CBC as the default cipher if the client supports it.
  • New options to prevent access from serialized Sub Locks and L3 Locks to Central Lock’s LAN ports
  • Access from serialized Locks to Central Lock’s web UI is now prevented by default
  • Web UI displays now also the physical IP for devices behind L3 locks when 1:1 NAT is in use
  • Serialized L3 Locks can now access the static routes that are configured on the Central Lock
  • The Internet can be accessed also from service port
  • Idle bandwidth consumption reduced
  • Usability improvements on edit connections page
  • VPN connections are now disconnected/reconnected only when needed when saving Central Lock settings
  • DNS rebind protection is now disabled to avoid possible problems
  • Fix for an issue where enabling MAC/IP filter broke access from LAN to L3 Locks
  • Fix for an issue where the remote support connection was not closed correctly
  • Fix for an issue where changing Key’s access rights changed the connection type to Layer 3
  • Fix for an issue where serializations might have gotten lost
  • Fix for an issue with static host routes (netmask 255.255.255.255)
  • Stability improvements