IIS Site V-278953: Fix fatal registry key path error - #1559
Open
FrederickGeek8 wants to merge 2 commits into
Open
IIS Site V-278953: Fix fatal registry key path error#1559FrederickGeek8 wants to merge 2 commits into
FrederickGeek8 wants to merge 2 commits into
Conversation
There is an error in the STIG descriptive text that was transcribed into V-278953's manual rule. Without this fix, this IIS 10.0 Site PowerSTIG cannot be run because the syntax for the registry key path is incorrect.
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
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.
Pull Request (PR) description:
This PR fixes a syntax error in the IIS Site 2.15 STIG introduced into
Processed/IISSite-10.0-2.15.xmlin 48674a30d084f4eda8f0a97c45d31ae81e448e4c (although the error was introduced to the manual rule log in an earlier commit).It's perhaps worth noting that the syntax error appears in the STIG text itself.
I updated the Manual Rule specification, regenerated the XML using
ConvertTo-PowerStigXml, and testing the new build in a testing VM I have set up. I no longer encounter the crash with the proper syntax.This Pull Request (PR) fixes the following issues:
When running PowerSTIG v4.30.0 with IIS Site ruleset enabled, PowerSTIG crashes with the following error:
This is due to a registry key path starting like
HKLM\instead ofHKLM:\. This PR fixes that syntax in the Manual Rule specification and regenerates the IIS-Site XML.This PR will also close #1535 by finishing the work started in 4.30.0.
Task list: