Abuse Whois Analyzer (Closes #2308)

[pranjalg1331]

(Please add to the PR name the issue/s that this PR would close if merged by using a Github keyword. Example: <feature name>. Closes #999. If your PR is made by a single commit, please add that clause in the commit too. This is all required to automate the closure of related issues.)

Description

Closes #2308
Please include a summary of the change and link to the related issue.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue).
• [ x] New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

• [ x] I have read and understood the rules about how to Contribute to this project
• [ x] The pull request is for the branch develop
• [ x] A new plugin (analyzer, connector, visualizer, playbook, pivot or ingestor) was added or changed, in which case:
  • [ x] I strictly followed the documentation "How to create a Plugin"
  • [ x] Usage file was updated. A link to the PR to the docs repo has been added as a comment here.
  • Advanced-Usage was updated (in case the plugin provides additional optional configuration). A link to the PR to the docs repo has been added as a comment here.
  • [ x] I have dumped the configuration from Django Admin using the dumpplugin command and added it in the project as a data migration. ("How to share a plugin with the community")
  • If a File analyzer was added and it supports a mimetype which is not already supported, you added a sample of that type inside the archive test_files.zip and you added the default tests for that mimetype in test_classes.py.
  • [ x] If you created a new analyzer and it is free (does not require any API key), please add it in the FREE_TO_USE_ANALYZERS playbook by following this guide.
  • Check if it could make sense to add that analyzer/connector to other freely available playbooks.
  • I have provided the resulting raw JSON of a finished analysis and a screenshot of the results.
  • If the plugin interacts with an external service, I have created an attribute called precisely url that contains this information. This is required for Health Checks.
  • [ x] If the plugin requires mocked testing, _monkeypatch() was used in its class to apply the necessary decorators.
  • I have added that raw JSON sample to the MockUpResponse of the _monkeypatch() method. This serves us to provide a valid sample for testing.
• If external libraries/packages with restrictive licenses were used, they were added in the Legal Notice section.
• [ x] Linters (Black, Flake, Isort) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
• I have added tests for the feature/bug I solved (see tests folder). All the tests (new and old ones) gave 0 errors.
• If the GUI has been modified:
  • I have a provided a screenshot of the result in the PR.
  • I have created new frontend tests for the new component or updated existing ones.
• [ x] After you had submitted the PR, if DeepSource, Django Doctors or other third-party linters have triggered any alerts during the CI checks, I have solved those alerts.

Important Rules

• If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
• Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review. After being reviewed and received a "change request", you should explicitly ask for a review again once you have made the requested changes.

[pranjalg1331]

@fgibertoni, I am trying to install the abuse_whois package through project-requirements.txt, but it always fails, so I have installed it through Dockerfile. Please suggest what can be done here.

[fgibertoni]

Please post also the error you're getting while installing the package so I can help you better

[pranjalg1331]

One of the abuse_whois dependency is causing conflicts

571.0 The conflict is caused by:
571.0     oletools 0.60.2 depends on pyparsing<4 and >=2.1.0
571.0     ioc-finder 7.0.0 depends on pyparsing<3.0 and >=2.4.7
571.0     matplotlib 3.0.2 depends on pyparsing!=2.0.4, !=2.1.2, !=2.1.6 and >=2.0.1
571.0     pydot 3.0.4 depends on pyparsing>=3.0.9
571.0     oletools 0.60.2 depends on pyparsing<4 and >=2.1.0
571.0     ioc-finder 7.0.0 depends on pyparsing<3.0 and >=2.4.7
571.0     matplotlib 3.0.2 depends on pyparsing!=2.0.4, !=2.1.2, !=2.1.6 and >=2.0.1
571.0     pydot 3.0.3 depends on pyparsing>=3.0.9
571.0     oletools 0.60.2 depends on pyparsing<4 and >=2.1.0
571.0     ioc-finder 7.0.0 depends on pyparsing<3.0 and >=2.4.7
571.0     matplotlib 3.0.2 depends on pyparsing!=2.0.4, !=2.1.2, !=2.1.6 and >=2.0.1
571.0     pydot 3.0.2 depends on pyparsing>=3.0.9
571.0     oletools 0.60.2 depends on pyparsing<4 and >=2.1.0
571.0     ioc-finder 7.0.0 depends on pyparsing<3.0 and >=2.4.7
571.0     matplotlib 3.0.2 depends on pyparsing!=2.0.4, !=2.1.2, !=2.1.6 and >=2.0.1
571.0     pydot 3.0.1 depends on pyparsing>=3.0.9
571.0     oletools 0.60.2 depends on pyparsing<4 and >=2.1.0
571.0     ioc-finder 7.0.0 depends on pyparsing<3.0 and >=2.4.7
571.0     matplotlib 3.0.2 depends on pyparsing!=2.0.4, !=2.1.2, !=2.1.6 and >=2.0.1
571.0     pydot 3.0.0 depends on pyparsing>=3.0.9
571.0     oletools 0.60.2 depends on pyparsing<4 and >=2.1.0
571.0     ioc-finder 7.0.0 depends on pyparsing<3.0 and >=2.4.7
571.0     matplotlib 3.0.2 depends on pyparsing!=2.0.4, !=2.1.2, !=2.1.6 and >=2.0.1
571.0     pydot 2.0.0 depends on pyparsing>=3
571.0 
571.0 To fix this you could try to:
571.0 1. loosen the range of package versions you've specified
571.0 2. remove package versions to allow pip to attempt to solve the dependency conflict
571.0 
[+] Building 0/1olutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
 ⠇ Service uwsgi  Building                                                                                                                                            575.8s 
failed to solve: process "/bin/sh -c pip3 install --no-cache-dir --compile -r project-requirements.txt     && pip3 install --no-cache-dir pycti==${PYCTI_VERSION}     && pip3 install --no-cache-dir --compile -r certego-requirements.txt" did not complete successfully: exit code: 1

[pranjalg1331]

@fgibertoni Creating a separate requirements file for abuse_whois does not give any error.

[fgibertoni]

Also please remember to update your migration number as they're now outdated 😉