Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add DataSourceProcessor Jython support #6027

Merged

Conversation

rubnogueira
Copy link
Contributor

I had a conflict with #5888 PR and made a mistake updating it with the new changes. I closed it and created this new PR. I'm sorry.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • My code follows the code style of this project.
  • My change requires a change to the documentation.

This PR:

With this PR, it is possible to create data source processor modules with python.

image

How to

Add Image Wizard Panel only verify processor modules based on @Serviceprovider annotation with DataProcessor.class. This PR adds JythonModuleLoader to search for DataSourceProcessors like Ingest and Report modules.

Thanks also to: @98jfran @mfrade @PatricioDomingues

@rubnogueira
Copy link
Contributor Author

@markmckinnon some updates:

In Autopsy 4.18.0, there was a new method overload in the run method that broke the FAMA module. I also implemented an abstract adapter class for DataSourceProcessor in Autopsy, which allows multiple processors (it's done like Ingest and Report modules).

FAMA is already using the new adapter schema and you can check here: https://github.com/labcif/FAMA

It's already fixed and I also made a new and much simpler DSP Module, so you can use it for your tests. It's a remote zip DSP which downloads the zip and put it as case artefacts. https://github.com/rubnogueira/autopsy-remote-case-dsp

LMK if you have any questions.

@eugene7646 eugene7646 merged commit 577bfd4 into sleuthkit:develop Sep 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants