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

Why checkout to a specific version in Datasploit ? #1

Open
Chan9390 opened this issue Nov 4, 2017 · 1 comment
Open

Why checkout to a specific version in Datasploit ? #1

Chan9390 opened this issue Nov 4, 2017 · 1 comment

Comments

@Chan9390
Copy link
Member

Chan9390 commented Nov 4, 2017

This question was raised by @anantshri

Why did I checkout to specific version of Datasploit ?

As some modules of this tool depends on API keys provided by the user, there will be an error if the latest version of Datasploit [in the future] doesnt find an API key in the committed version of config.py file.

To temporarily avoid that, I have checked out to a specific version to make sure that the Dockerfile could be used at any time. Once a new update is available with additional API key spaces, I will manually updated the config.py file and checkout to the latest version at that particular time.

I think it is better to keep this issue open until the framework itself changes / updates its error handling mechanisms.

@Chan9390
Copy link
Member Author

Chan9390 commented Nov 4, 2017

I was also informed that @anantshri has already raised an issue about the error handling mechanism. (DataSploit/datasploit#176)

This issue cannot be closed until the upstream issue is resolved.

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

1 participant