One Drive Enum Username Output #16
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
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.
I added in a few lines of code that create an output file for the users discovered based off of the domain that was input. I'm then writing the email addresses that are found to be valid to this file in real time. I was previously having trouble with the initial file creation from the main branch if the tool stopped execution or aborted early. If either of these conditions happened then the output file would not be created and grabbing the users was impossible. So I thought that writing them as they were found to a file created prior to execution would alleviate that problem. I've ran this on my own many times and it works consistently and would love to see this implemented to the main branch if it makes sense.