Adding Kerberos Support #47
Open
Conversation
This file contains 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
Adds the -k option which is Kerberos. The intended steps are 1. Kinit or obtain a ccache for the desired user 2. use -k 2. supply username in either domain\\user format or just user format. 3. provide a FQDN for the DC 4. profit.
Brought up to date and made sure only changes related to kerberos exist
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A fairly simple method of adding in Kerberos support. Very little code is added to achieve this and most of it is boiler plate to tell which type of connection we should be making. Additionally if Kerberos is selected a startTLS() call is made. Lastly gssapi was added as a requirement.
The usage of this new feature would work as follows:
This has been tested on kali machines. Tests were preformed using all previous methods of commands I could think of to ensure to logic was removed as well as in multiple domain setups to include ones with channel binding and signing requirements. No issues were found.