UIM dirscan probe creates a faulty MD5 when the signature is deleted manually

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

The dirscan probe generates a faulty MD5 signature when the signature is deleted manually.

The bad checksum created looks like:

md5_sig = DEDEDEDEDEDEDEDEDEDEDEDEDE

or:

md5_sig = 38383838383838383838383838383838

It can be different characters but always the xyxyxyxy pattern.

CONSIDERATIONS:
•  After clicking "Recalculate Checksum" in the probe GUI the checksum is update to a correct one. 

Example:
md5_sig = BEEC38C8B48B2008506F26C9E92449EF

•  this happens with every file I tested and on different platforms. 

•  When the checksum is deleted manually and the probe restarted the probe logs the following: 

May 28 09:56:54:621 [140158516856640] dirscan: ****************[ Starting ]****************
May 28 09:56:54:621 [140158516856640] dirscan: * File and directory checking probe 3.17
May 28 09:56:54:621 [140158516856640] dirscan: * Nimsoft Corporation
May 28 09:56:54:622 [140158516856640] dirscan: ReadCfg - profile (test1)file_0001, no MD5 signature specified for file /.bash_history, generating one
May 28 09:56:54:622 [140158516856640] dirscan: ReadCfg - Updating configuration file dirscan.cfg

So it looks like the probe, doesn't see the checksum so it creates one. In this scenario, the creating is faulty, as it creates an odd signature with 2 repeating characters.

 

Environment

UIM 9.2/20.1 
dirscan 3.17 on windows 2016 / 2012 or Linux Centos 7

Cause

Code issue

Resolution

This issue is fixed in 3.17T1  (dirscan_3.17_26052021.zip)

The hotfix can be downloaded here or log a support case and request this fix.