disable blocking download of an executable #180
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.
This is subjective but imho blocking downloaded executables should be disabled by default and enabled if the researcher wants to. This is to avoid issues like #151 .
Event 27 will not only block downloads but also applications that rely on extracting an embedded executable at runtime such as ProcMon, ProcExp and Sysmon itself. Users who have an automated pipeline that will install Sysmon research configuration at the middle in the pipeline will have their pipeline broken because all installations after Sysmon will fail.
As I said, this is very subjective and some researchers might like to have this enabled by default. An alternative is to update the readme and mention that downloads\installation will fail.