File Integrity Checking

Current Situation

• YADE makes use of hash files with the exension .md5 corresponding to transferred files.
• The following configuration items are used for a integrity hashes:
  • SourceFileOptions
    • CheckIntegrityHash
      • HashAlgorithm (default: MD5)
  • TargetFileOptions
    • CreateIntegrityHashFile
      • HashAlgorithm (default: MD5)
• If CheckIntegrityHash=true then the hash of the target file is calculated and is compared to the source if a *.md5 file is available from the source.
  • If CheckIntegrityHash=false then CreateIntegrityHashFile=true has no effect and the hash file will not be created.
• If a file transfer makes use of a jump host, then the integrity hash is calculated for transfer to the jump host, but not to the target host. The same applies to creation of a hash file.

Desired Behavior

• When used with a jump host and CheckIntegrityHash=true,
  • then an integrity hash will be calculated for transfer to the jump host and to the target host. Implicitely a hash file is created on the jump host.
  • if CreateIntegrityHashFile=true, then the hash file will be created on the target host.

Test Instructions

• Test integrity hash functionality without a Jump Host.
  • Tip: On the first run, enable TargetFileOptions -> CreateIntegrityHashFile to create .md5 files.
    • These files can then be copied to the source for the subsequent tests.
• Test integrity hash functionality with a Jump Host.
  • Test all operations.
    • Note: Only Copy and Move use the integrity hash, but all operations should be tested to identify any unintended side effects.
• Test both Jump Host configurations:
  • Jump Host configured on the Source.
  • Jump Host configured on the Target.
• If SourceFileOptions -> CheckIntegrityHash is enabled, the expected result is that the integrity hash is verified twice:
  • Between Source and Jump Host.
  • Between Jump Host and Target.
  • To verify this, check the logs for entries containing [CheckIntegrityHash].
• Test with SourceFileOptions -> CheckIntegrityHash disabled.
  • Expected result: no side effects, no [CheckIntegrityHash] in the log
• Test with TargetFileOptions -> CreateIntegrityHashFile enabled and disabled.
  • Expected result:
    • SourceFileOptions -> CheckIntegrityHash enabled, TargetFileOptions -> CreateIntegrityHashFile disabled
      • as previously described  the expected result is that the integrity hash is verified twice.
    • TargetFileOptions -> CreateIntegrityHashFile enabled
      • for each transferred file, an .md5 file is created on the Target.