Difference between revisions of "Autopsy Developer's Guide"

From SleuthKitWiki
Jump to: navigation, search
(Created bare initial page.)
 
(Autopsy 3 Topics)
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This page contains technical information on developing code for Autopsy.  
+
This page contains technical information on developing code for [[Autopsy]].  
  
This page is a work in progress and more information will be postedHere are some starting points.  
+
There are two types of development that can occur with Autopsy:
* The [[Developer Guidelines]] define how code and patches can be submitted and incorporated into the distribution.  
+
* Development of Plug-in modules that you distribute
* The [http://lists.sourceforge.net/lists/listinfo/sleuthkit-developers Sleuth Kit Developers] list exists to discuss the development of the tools.  Subscribe to ask and answer questions.  
+
* Development of core infrastructure and the Autopsy framework
 +
 
 +
If you are looking for ideas on how you can contribute, then you may want to refer to the feature request and bug [[trackers]].  They contain ideas that people have for the tools or bugs that need to be fixed.
 +
 
 +
= Module Development =
 +
Autopsy was developed to be a platform for plug-in modulesThe [http://www.sleuthkit.org/autopsy/docs/api-docs/ Developer's Guide] contains the API docs and information on how to write modules. When you create a module, add it to the list of [[Autopsy 3rd Party Modules]].
 +
 
 +
= Platform Development =
 +
 
 +
* The [[Developer Guidelines]] defines how code and patches can be submitted and incorporated into the sleuthkit.org projects.  
 +
* The [[sleuthkit-developers]] list exists to discuss the development of the sleuthkit.org tools.  Subscribe to ask and answer questions.  
 
* If you want to contribute documentation, then refer to the [http://www.sleuthkit.org/support.php Support] page.  
 
* If you want to contribute documentation, then refer to the [http://www.sleuthkit.org/support.php Support] page.  
  
  
= Technical Details =
+
The source code is stored in a [http://www.github.com/ github] repository. You can get the latest source tree from http://github.com/sleuthkit/autopsy.
To be defined...
+
 
 +
== Autopsy 3 Topics ==
 +
 
 +
* [[Autopsy 3 Logging and Error Checking]] is a reference for how errors and log messages are made.
 +
* [[Autopsy 3 Module Versions]] is a reference on the versioning scheme of the internal modules.
 +
* Adding extensions to the [[Autopsy File Extension Mismatch Module]]
 +
* Debugging the [[Autopsy Keyword Search Module]]
 +
* [[Adding Artifacts and Attributes]] to the official code base

Latest revision as of 10:44, 27 January 2015

This page contains technical information on developing code for Autopsy.

There are two types of development that can occur with Autopsy:

  • Development of Plug-in modules that you distribute
  • Development of core infrastructure and the Autopsy framework

If you are looking for ideas on how you can contribute, then you may want to refer to the feature request and bug trackers. They contain ideas that people have for the tools or bugs that need to be fixed.

Module Development

Autopsy was developed to be a platform for plug-in modules. The Developer's Guide contains the API docs and information on how to write modules. When you create a module, add it to the list of Autopsy 3rd Party Modules.

Platform Development

  • The Developer Guidelines defines how code and patches can be submitted and incorporated into the sleuthkit.org projects.
  • The sleuthkit-developers list exists to discuss the development of the sleuthkit.org tools. Subscribe to ask and answer questions.
  • If you want to contribute documentation, then refer to the Support page.


The source code is stored in a github repository. You can get the latest source tree from http://github.com/sleuthkit/autopsy.

Autopsy 3 Topics