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

Merge remote-tracking branch 'upstream/custom-release-march-2018' into volatility-fixes

Browse Source
This commit is contained in:
Richard Cordovano 2018-03-29 19:55:50 -04:00
commit bd7524b3dd
1 changed files with 44 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

70
Core/src/org/sleuthkit/autopsy/corecomponentinterfaces/DataContentViewer.java
View File

@ -85,31 +85,49 @@ public interface DataContentViewer {
public boolean isSupported(Node node); public boolean isSupported(Node node);
/** /**
* Checks whether the given viewer is preferred for the Node. This is a bit * Checks whether the given viewer is preferred for the Node. This is a bit
* subjective, but the idea is that Autopsy wants to display the most * subjective, but the idea is that Autopsy wants to display the most
* relevant tab. The more generic the viewer, the lower the return value * relevant tab. The more generic the viewer, the lower the return value
* should be. This will only be called on viewers that support the given * should be. This will only be called on viewers that support the given
* node. * node (i.e., isSupported() has already returned true).
* *
* Level 0: Not supported/should never be the default viewer * The following are some examples of the current levels in use. If the selected
* * node is an artifact, the level may be determined by both the artifact and its
* Level 1: Always work, not very specific * associated file.
* *
* Level 2: Unused * Level 7 - Based on the artifact, if any, in the selected node and specific
* * to an artifact type or types. Current content viewers that can return level 7 are
* Level 3: Artifact-based that flag files * the Messages tab (only supported for email and SMS) and the Indexed Text tab
* * when the selected node is a Keyword Search hit.
* Level 4: File-based that are not always enabled, but also not really specific *
* * Level 6 - Based on the artifact, if any, in the selected node but not
* Level 5: File-based that are specific: * restricted to particular types. The current content viewer that can return level 6
* * is the Results tab. It returns this level for most artifact types,
* Level 6: Artifact-based that is not really specific * unless the associated file is assumed to be of greater interest (for example,
* * a Hash Set Hit will not be level 6 because the file itself is of greater interest).
* Level 7: Artifact-based and specific *
* * Level 5 - Based on the file in the selected node and very specific to the file type. The current
* @param node Node to check for preference * content viewer that will return level 5 is
* * the Application tab, which supports media files (such as images) and
* @return an int (0-10) higher return means the viewer has higher priority * certain types of databases.
*/ *
* Level 4 - Based on the file in the selected node but fairly general.
* Currently this is the level returned by the Indexed Text tab if Keyword Search
* has been run (unless the node is a Keyword Search hit or a Credit Card account).
* This is the default tab for most files.
*
* Level 3 - Based on the artifact, if any, in the selected node where the
* artifact is thought to be of less interest than the associated file. This
* level is returned by the Results tab for artifacts like Hash Set Hits.
*
* Level 1 - Very general and should always be available. The Hex, Strings, and Metadata tabs
* are all this level
*
* Level 0 - For cases where the content viewer should never be displayed by default.
*
* @param node Node to check for preference
*
* @return an int (0-10) higher return means the viewer has higher priority
*/
public int isPreferred(Node node); public int isPreferred(Node node);
} }