Overview
With the release of OneLaw version 4.3.0, a new digitally signed library file - Humanizer.dll - has been introduced as part of the application package.
This file is digitally signed to ensure authenticity and maintain code integrity in line with modern security standards.
Who needs to take action?
This update is relevant only for organisations that enforce strict application control policies, including:
- Microsoft AppLocker
- Windows Defender Application Control (WDAC)
- Certificate-based whitelisting solutions
- Other application execution restriction tools
If your environment does not restrict software execution based on digital signatures, no action is required.
Required Action (If Applicable)
To avoid disruption for end users following the upgrade to OneLaw 4.3.0, IT administrators should review existing allow-lists and, where necessary, add the new certificate details associated with:
- Humanizer.dll
- Publisher: Humanizer (.NET Foundation)
- Issued by: .NET Foundation Projects Code Signing CA
Full certificate information - including serial number and thumbprint - is provided in the attached technical document.
Why this matters
If the certificate is not added to your allow-list in restricted environments, the new library may be blocked from execution. This could prevent OneLaw 4.3.0 from functioning correctly for users.
Proactively updating your security policies will ensure a smooth deployment with no interruption to service
For full technical certificate details, please refer to:
Code Signing Changes for OneLaw 4.3.0