8000 adding 3rd party report to mail by adrima01 · Pull Request #908 · Lookyloo/lookyloo · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

adding 3rd party report to mail #908

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

Merged
merged 2 commits into from
Apr 17, 2024
Merged

Conversation

adrima01
Copy link
Contributor

Pull requests should be opened against the main branch. For more information on contributing to Lookyloo documentation, see the Contributor Guidelines.

Type of change

Description:
Adding a 3rd party module section to the email template.
We want to display if an URL is malicious or not according to the 3rd party modules to provide more information.

Select the type of change(s) made in this pull request:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation (change or fix to documentation)

Fixes #issue-number

Proposed changes

@Rafiot Rafiot self-assigned this Apr 15, 2024
@adrima01
Copy link
Contributor Author
adrima01 commented Apr 16, 2024

Maybe it's not a good idea to reuse the modules function in init.py to filter the response from the 3rd party modules?
I tried to use it to avoid duplication, maybe put the filter somewhere else?

@AntoniaBK
Copy link
Contributor

I tried to use it to avoid duplication, maybe put the filter somewhere else?

I too would rather put all the filtering in an extra function that can be called when sending the mail and when displaying the 3rd-party lookups on the website.
So mail and website are not mixed together in one function.

@adrima01
Copy link
Contributor Author
adrima01 commented Apr 16, 2024

I think the concept of checking if the response is empty doesn't work.Urlscan triggers a scan (which wasn't the case at my lookyloo instance because it wasn't enabled)
So even if it isn't malicious, there will be something in the response (url to the urlscan scan)

Copy link
Member
@Rafiot Rafiot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, as you discussed, you should not reuse the method in __init__.py to do the post processing and put it in the mail. It makes more sense to create a new method in the Lookyloo class.

You might have to check one after the other all the keys in the response dict to make sure there is a response from any of the module.

@adrima01 adrima01 force-pushed the 3rd_party_report_mail branch from 8bbf2bf to c5c1a8a Compare April 16, 2024 13:30
@adrima01 adrima01 marked this pull request as ready for review April 17, 2024 08:58
@Rafiot Rafiot merged commit 4c2620d into Lookyloo:main Apr 17, 2024
@adrima01 adrima01 deleted the 3rd_party_report_mail branch May 2, 2024 09:56
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.

3 participants
0