[Feature request] Option to "re-read source after acquisition for verification" #910

Open
opened 2026-01-29 15:32:46 +00:00 by claunia · 2 comments
Owner

Originally created by @robin-francois on GitHub (Oct 12, 2022).

Originally assigned to: @claunia on GitHub.

Type

New command...

Description

Popular tools in the digital archiving community such as FTK Imager or Guymager have an option to perform some checks. Those checks are described in Guymager as:

  • "Re-read source after acquisition for verification (take twice as long)";
  • "Verify image after acquisition (take twice as long)".

Image verification is performed when the sidecar file is generated, so the second action seems to be already a mandatory step. The first action of "re-reading" is very similar to doing a new dump and comparing it to an existing image. The only difference in the other popular tools, is that there is no additional file kept after the action.

Context

An option to perform such check could be an incentive for people using other tools to switch to Aaru, since such option might be part of existing workflows or requirements.

Documentation

No response

Originally created by @robin-francois on GitHub (Oct 12, 2022). Originally assigned to: @claunia on GitHub. ### Type New command... ### Description Popular tools in the digital archiving community such as FTK Imager or Guymager have an option to perform some checks. Those checks are described in Guymager as: - "Re-read source after acquisition for verification (take twice as long)"; - "Verify image after acquisition (take twice as long)". Image verification is performed when the sidecar file is generated, so the second action seems to be already a mandatory step. The first action of "re-reading" is very similar to doing a new dump and comparing it to an existing image. The only difference in the other popular tools, is that there is no additional file kept after the action. ### Context An option to perform such check could be an incentive for people using other tools to switch to Aaru, since such option might be part of existing workflows or requirements. ### Documentation _No response_
claunia added the feature requestbeginner labels 2026-01-29 15:32:46 +00:00
Author
Owner

@tomensom commented on GitHub (Nov 8, 2022):

Just adding my support for this feature. It would be a requirement for switching our workflow to Aaru for one organisation I work for.

@tomensom commented on GitHub (Nov 8, 2022): Just adding my support for this feature. It would be a requirement for switching our workflow to Aaru for one organisation I work for.
Author
Owner

@TheRogueArchivist commented on GitHub (Nov 17, 2022):

I can also confirm that other (non-forensic) tools, such as ImgBurn, have a similar feature as well, so this wouldn't be exclusively for forensic use cases.

@TheRogueArchivist commented on GitHub (Nov 17, 2022): I can also confirm that other (non-forensic) tools, such as ImgBurn, have a similar feature as well, so this wouldn't be exclusively for forensic use cases.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: aaru-dps/Aaru-aaru-dps#910