Repository navigation
Add RPC encryption CA reg key #168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🔴 Critical | ⚡ Quick win
The build fails on this line. Pin a SharpHoundCommon version that contains the new API.
The
buildcheck reports thatCertAbuseProcessorhas noIsRPCEncryptionEnforcedmember andCARegistryDatahas noRPCEncryptionEnforcedmember. The PR description states that this change corresponds with SharpHoundCommon PR 239, so the required members only exist in that unmerged branch. Merge and publish the SharpHoundCommon change first, then update_ResolvedCommonVersionin this repository so CI resolves a package that contains both members.🧰 Tools
🪛 GitHub Actions: Build / 0_build.txt
[error] 838-838: dotnet build failed with error CS0117: 'CARegistryData' does not contain a definition for 'RPCEncryptionEnforced'.
🪛 GitHub Actions: Build / build
[error] 838-838: dotnet build failed with CS0117: 'CARegistryData' does not contain a definition for 'RPCEncryptionEnforced'.
🪛 GitHub Check: build
[failure] 838-838:
'CertAbuseProcessor' does not contain a definition for 'IsRPCEncryptionEnforced' and no accessible extension method 'IsRPCEncryptionEnforced' accepting a first argument of type 'CertAbuseProcessor' could be found (are you missing a using directive or an assembly reference?)
[failure] 838-838:
'CARegistryData' does not contain a definition for 'RPCEncryptionEnforced'
[failure] 838-838:
'CertAbuseProcessor' does not contain a definition for 'IsRPCEncryptionEnforced' and no accessible extension method 'IsRPCEncryptionEnforced' accepting a first argument of type 'CertAbuseProcessor' could be found (are you missing a using directive or an assembly reference?)
[failure] 838-838:
'CARegistryData' does not contain a definition for 'RPCEncryptionEnforced'
🤖 Prompt for AI Agents
Source: Linters/SAST tools