Fix security callback enumeration for 32bit #71
Conversation
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
From RpcCore2, the _RPC_INTERFACE_T structure layout seems to be incorrect regarding the security callback. The changes in this commit were confirmed to fix the issue for RpcCore4 and probably also work for the previous two versions.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
From RpcCore2 on, the
_RPC_INTERFACE_Tstructure layout seems to be incorrect regarding the security callback. I recently encountered a 32bit RPC server utilizing security callbacks and they were not displayed in RpcView.The changes in this PR were confirmed to fix the issue for RpcCore4 and probably also work for the previous two versions.