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

Support for Config File #31

Open
ngkogkos opened this issue Dec 24, 2016 · 5 comments
Open

Support for Config File #31

ngkogkos opened this issue Dec 24, 2016 · 5 comments
Assignees
Milestone

Comments

@ngkogkos
Copy link
Collaborator

ngkogkos commented Dec 24, 2016

Create simple config file and parse it to support stuff like:

  • Preferred scanners
  • Exploit and Info limits
  • HTTP config like http-agent
  • Any API keys?

Did we say that Google API key will be better or @Sinderella you only make GET queries? What if CAPTCHA comes up? Sorry, I know we've discussed this in work, but short memory 💃 .

Also, if we ever add DB or you can think of something else, add it here.

This is for the very future.

@Sinderella Sinderella added this to the Beta release milestone Dec 30, 2016
@Sinderella
Copy link
Owner

Sinderella commented Jan 4, 2017

So far, no API key is needed and hopefully never will. I'm sure I am not the only user who want tools that are able to run without any difficulties, like configurations.

@Sinderella
Copy link
Owner

Config file format https://martin-thoma.com/configuration-files-in-python
I vote for YAML, and the second choice would be python configuration file.

@ngkogkos
Copy link
Collaborator Author

ngkogkos commented Jan 4, 2017

Well yeah python config file is out of the discussion :D. So either JSON or YAML. I like YAML as well.

@Sinderella
Copy link
Owner

YAML then

@Sinderella Sinderella self-assigned this Jan 6, 2017
@Sinderella
Copy link
Owner

Postpone until this is fixed PythonCharmers/python-future#226

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants