Details
-
Feature
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
- Current Situation
- A checksum file with the extension .md5 is created if
- the parameter CreateSecurityHashFile is set to true and
- the parameter CreateSecurityHash is set to true.
- This feature is only available if
- the source protocol local is used or
- a jump host is being used with the operation copytointernet.
- If the parameter file_compress is used then the md5 value in the checksum file is calculated from the non-compressed input file. The checksum file itself is compressed.
- A checksum file with the extension .md5 is created if
- Desired Behavior
- If CreateSecurityHashFile=true the integrity hash of the target file is stored in a file on the target. This file has the same name plus the integrity hash type (md5) as extension.
- This feature works independent form the setting of the parameter CreateSecurityHash.
- This feature shall be available independently from the protocol used for source and target systems.
- If the parameter file_compress is used then the checksum file itself is not compressed.
- If the parameters replacement and replacing are used then the name of the checksum file is created from the resulting name of the file on the target system.
- The existing parameters SecurityHash... will be renamded to IntegrityHash....
Attachments
Issue Links
- affects
-
YADE-368 YADE Background Service returns "parameter [md5] can't be empty"
- Released
- is duplicated by
-
YADE-241 YADE should generate MD5 hash file when parameter CreateSecurityHashFile = true is set
- Dismissed
-
YADE-346 Integrity hash file should be created
- Dismissed
- is related to
-
YADE-87 SecurityHashType: specify the type of a requested sequrity hash (-file)
- Dismissed
- requires
-
YADE-261 File Integrity Checking
- Deferred
- mentioned in
-
Page Loading...
(1 mentioned in)