HealthChecker IIS Modules Check#1132
Merged
Merged
Conversation
dpaulson45
requested changes
Jul 21, 2022
dpaulson45
requested changes
Aug 4, 2022
dpaulson45
added
the
New Feature/Check
dpaulson45
requested changes
Aug 5, 2022
Member
|
@lusassl-msft after making that one change rebase against main and squash all the commits down to 1. We could have different commits for the Pester Tests, but they were also with the main commits as well, that is why it might be best to have just one here. |
lusassl-msft
force-pushed
the
lusassl-iismodulework
branch
from
d5d90bd to
fb43133
Compare
dpaulson45
approved these changes
Aug 5, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description:
Implemented a new test which validates the modules, loaded by IIS. We read the required module information from the
applicationHost.configfile and validating if they're signed and whether the signer isO=Microsoft Corporationor not. We do this with the help of theGet-AuthenticodeSignaturecmdlet.We call out if:
HashMismatchor isNotTrusted(yellow warning)UnknownError,NotSigned,NotSupportedFileFormatorIncompatible(red error)Resolve: #1123
Validation:
Lab & Unit testing