Details
-
Feature
-
Status: Deferred (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
- Starting Situation
- JADE has the following parameters around the integrity hash
- CreateSecurityHash (default: true)
- CreateSecurityHashFile (default: false)
- CheckSecurityHash (default: false)
- SecurityHashType (default: MD5)
- If CreateSecurityHash=true then only the integrity hash of the target file is calculated.
- If CheckSecurityHash=false then CreateSecurityHashFile=true has no effect and the integrity hash file is not created.
However, JADE tries to transfer an integrity hash file which doesn't exist and subsequently an error is thrown.
- If CheckSecurityHash=false then CreateSecurityHashFile=true has no effect and the integrity hash file is not created.
- A check of the integrity hash is not implemented. In particular, the integrity hash of the source file has to be calculated too.
- If CheckSecurityHash=true then JADE tries to transfer a security hash file which doesn't necessarily exist and an error is raised.
- If CreateSecurityHashFile=true then the security hash file will be created on the source but
- ... it can only be created if the source has the "local" protocol
- ... an error occurred if the source protocol is not "local".
- JADE has the following parameters around the integrity hash
- Desired Behavior
- A integrity hash is created for source files and for target files (not for intermediate files on a jump host) to check if the transfer was complete and accurate.
- Integrity is checked by creating an integrity hash per source file and per target file and by comparing the checksum results.
- The parameter CreateSecurityHash will be removed as it is replaced by the parameter CheckSecurityHash.
- If CheckSecurityHash=true then the integrity hash of the source and the target file are calculated and will be checked after the transfer.
- If the hashes are unequal then the transfer rolls back.
- The existing parameters SecurityHash... will be renamded to IntegrityHash....
Attachments
Issue Links
- is duplicated by
-
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
- is required by
-
YADE-262 Checksum File
- Resolved
- relates to
-
YADE-349 Integrity Checking of source files
- Resolved
- mentioned in
-
Page Loading...