Implement SQL Authentication #11
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add user and password arguments to all functions, if non-NULL these are embedded into the used connection string as UID=%s;PWD=%s; thereby using the provided credentials for SQL authentication instead of relying on Windows authentication based on the current execution context.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In recent engagements I needed the possibility to authenticate using explicit SQL credentials.
The nature of these changes is quite mechanical and they need adaption of the various C2 integration scripts which this pull request mostly lacks.
At the time I wrote this, I wasn't aware of @dejisec recent pull request #9. As a result, this contains an alternative implementation of the wrapper scripts needed for Outflank C2.
I choose to add optional user and password arguments for SQL authentication:
Whereas omitting them uses the existing Windows based authentication from the current execution context:
While not mergeable as is, I hope it is still useful for somebody out there in the same situation.