Protect - Changelog

Shun

February 01, 2021 09:09

This page lists every addition/modification to Dualog Protect since its first release.

IMPROVEMENTS:

Unbound Upgrade
Upgraded to version 1.13
Stability and Performance
Prevents potential situations where exceptions are not handled properly

BUG FIXES:

Last Known Configurations
Fixed an issue where the latest configurations would now be remembered in situations where a computer installed with Protect has been restarted, along with the internet being unavailable, configurations will be lost upon restarted.

IMPROVEMENTS:

Unbound and NIM Upgrade
Upgraded to version 1.13
.NET Core Upgrade
Upgraded to version 5.0
Security Modifications
Version and Identity to be made invisible from public
Improved Logging
Improved logging for the simplification of error detections and etc
Added carriers and timestamp to the logs whenever cloud servers receive a message
Re-structuring of caching method (Client Keys)

IMPROVEMENTS:

Encryption key fetched from Dualog cloud
The encryption key is now obtained from the Digital Platform shore system
Improved logging
Protect is now writing all activities from the DNS server (Unbound) into the Protect log. It also logs when port 53 is occupied.

BUG FIXES:

Protect client stuck in starting
If unbound is not able to start, the Protect client is stuck in Starting, which again causes it to be hard to stop, for instance during an upgrade

NEW FEATURES:

Support Win32 Operating systems
Added support for 32-bit operating systems. Version 3 installed OK on 32-bit OS but did not start.
Retrieve logs from client
Log retrieval was added to version 7 of the Digital Platform (released 19. Mar 2020). The Protect client now supports this feature, which is only available for Dualog Superusers.

IMPROVEMENTS:

Modified Blacklist functionality
The blacklist feature is modified to also blacklist sub-domains, example: Blacklisting bbc.com will also blacklist live.bbc.com and bbc.com/programs

By using whitelisting, specific subdomains can be made available.
Blacklist and whitelist architecture redesigned
To achieve the modified Blacklist functionality, separate black- and whitelist servers are installed and configured in the cloud. This also means that requests for white- and blacklisted domains are logged and can be displayed in dashboards.