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.

Sign up for GitHub

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

Jump to bottom

Improve Phishtank maliciousness results #181

Closed
jeromeleonard opened this issue Feb 8, 2018 · 0 comments
Closed

Improve Phishtank maliciousness results #181

jeromeleonard opened this issue Feb 8, 2018 · 0 comments
Assignees
@jeromeleonard
Labels
category:enhancement Issue is related to an existing feature to improve
Milestone
1.9.0

Comments

@jeromeleonard
Copy link
Contributor

Request Type

improvement

Description

Phishtank analyzer does not consider every information available (in_database, verified, valid ) to determine if an url is a phish or not.

Possible Solutions

Set results to :
malicious : in_database = true, verified = true, valid = true
suspicious: in_database = true, verified = false, valid = false
safe: in_database = true, verified = true, valid = false
unknown: in_database = false, verified = false, valid = false
@jeromeleonard jeromeleonard self-assigned this Feb 8, 2018
jeromeleonard added a commit that referenced this issue Feb 9, 2018
@jeromeleonard
#181 improve maliciousness evaluation
a77bdb8
@jeromeleonard jeromeleonard added the category:enhancement Issue is related to an existing feature to improve label Feb 9, 2018
@jeromeleonard jeromeleonard added this to the 1.9.0 milestone Feb 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeromeleonard jeromeleonard

Labels
category:enhancement Issue is related to an existing feature to improve
Projects
None yet
Milestone
1.9.0
Development

No branches or pull requests
1 participant
@jeromeleonard