mstoeck3/autopsy-flatpak
1
0
Fork 0
mirror of https://github.com/overcuriousity/autopsy-flatpak.git synced 2025-07-17 18:17:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

7673 Allow helpers to call correct Blackboard.postArtifacts() API

Browse Source
This commit is contained in:
Richard Cordovano 2021-10-26 18:09:30 -04:00
parent 3747dba3e2
commit 68fd499b81
1 changed files with 16 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
Core/src/org/sleuthkit/autopsy/ingest/IngestManager.java
View File

@ -333,31 +333,34 @@ public class IngestManager implements IngestProgressSnapshotProvider {
* the artifacts WILL be analyzed after the ingest job is * the artifacts WILL be analyzed after the ingest job is
* started, when the ingest job executor, working in batch mode, * started, when the ingest job executor, working in batch mode,
* schedules ingest tasks for all of the data artifacts in the * schedules ingest tasks for all of the data artifacts in the
* case database. * case database. There is a slight risk that the wrong ingest
* job will be selected if multiple ingests of the same data
* source are in progress.
* *
* 2. The artifacts were posted by an ingest module that either * 2. The artifacts were posted by an ingest module that either
* has not been updated to use the current * has not been updated to use the current
* Blackboard.postArtifacts() API, or is using it incorrectly. * Blackboard.postArtifacts() API, or is using it incorrectly.
* In this use case, the code below should be able to find the * In this use case, the code below should be able to find the
* ingest job to which to add the artifacts via their data * ingest job to which to add the artifacts via their data
* source. * source. There is a slight risk that the wrong ingest job will
* * be selected if multiple ingests of the same data source are
* In both of the use cases above, there is a slight risk that * in progress.
* the wrong ingest job will be selected if multiple ingests of
* the same data source are in progress.
* *
* 3. The portable case generator uses a * 3. The portable case generator uses a
* CommunicatonsArtifactHelper constructed with a null ingest * CommunicationArtifactsHelper constructed with a null ingest
* job ID, and the CommunicatonsArtifactHelper posts artifacts. * job ID, and the CommunicatonsArtifactHelper posts artifacts.
* Clearly, no data artifact ingest modules will be running, as * Ingest of that data source might be running, in which case
* might not have been so in the original case. This is an * the data artifact will be analyzed. It also might be analyzed
* acceptable edge case, given the goals of portable cases. * by a suvsequent ingest job for the data source. This is an
* acceptable edge case.
* *
* 4. The user can manually create timeline events with the * 4. The user can manually create timeline events with the
* timeline tool, which posts the TSK_TL_EVENT data artifacts. * timeline tool, which posts the TSK_TL_EVENT data artifacts.
* The user selects the data source for these artifacts. INgest * The user selects the data source for these artifacts. Ingest
* of that data source might be running. This is an acceptabel * of that data source might be running, in which case the data
* edge case. * artifact will be analyzed. It also might be analyzed by a
* suvsequent ingest job for the data source. This is an
* acceptable edge case.
*/ */
DataArtifact dataArtifact = newDataArtifacts.get(0); DataArtifact dataArtifact = newDataArtifacts.get(0);
try { try {