Make the EICAR canary useful again #14475
Merged
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
acammack-r7
suggested changes
Dec 10, 2020
|
Tested this and everything seems to work as expected 👍 Before: After: |
Release NotesFixed a bug where the EICAR canary would be checked too late to be useful. |
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.
Resolves #14415
Refactor of where and when the EICAR canary is checked
Verification
data/eicar.comfile-q)You may also delete the
/gems/metasploit-payloads-2.0.24/data/android/apk/classes.dexfile which was mentioned in the issue and framework should no longer break due to the load order differences meaning the AV warning will always be displayed first