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

Add support for subdomain artifacts #6

Open
deadbits opened this issue May 22, 2018 · 1 comment
Open

Add support for subdomain artifacts #6

deadbits opened this issue May 22, 2018 · 1 comment
Assignees
@deadbits
Labels
enhancement in-progess testing Features being tested before deployment
Projects
Version 1.0 Version 1.0

Comments

@deadbits
Copy link
Contributor

the FQDN artifact regex pattern doesn't properly recognize subdomains. this needs to be addressed so users can run modules against subdomains they add or ones discovered by other modules as children
@deadbits deadbits added the bug label May 22, 2018
@deadbits deadbits self-assigned this May 22, 2018
@deadbits deadbits added this to In progress in Version 1.0 Jun 26, 2018
@deadbits deadbits added this to To do in Version 1.0 Aug 16, 2018
@deadbits deadbits added in-progess testing Features being tested before deployment and removed backlog labels Aug 28, 2018
@deadbits
Copy link
Contributor Author

In progress.. Artifacts are being re-worked so instead of one Artifact object each type will have it's own object with fields specific to it's type.

@deadbits deadbits moved this from To do to Needs review in Version 1.0 Aug 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@deadbits deadbits

Labels
enhancement in-progess testing Features being tested before deployment
Projects
Version 1.0
  
Testing
Version 1.0
  
In progress
Milestone
No milestone
Development

No branches or pull requests
1 participant
@deadbits