platform: add mapping of USER_INFO_10 structure to LMAccess #178
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
|
Great. Can you please update CHANGES.md? |
|
@dblock CHANGES.md updated. |
dblock
added a commit
that referenced
this pull request
Jan 20, 2013
platform: add mapping of USER_INFO_10 structure to LMAccess
mstyura
pushed a commit
to mstyura/jna
that referenced
this pull request
Sep 9, 2024
Motivation: A new version of the os-maven-plugin was released Modifications: Update to new version Result: Use latest version
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.
This pull request adds a mapping of the USER_INFO_10 structure to the platform component. I ended up needing this as I was trying to enumerate users using Netapi32.NetUserEnum, and was getting error code 124 when I used level 23. I suspect that the cause of the error code was operating system and/or domain controller configuration specific. Regardless, other levels worked fine for me. USER_INFO_0 and USER_INFO_1 were already supported, but neither includes access to the user's full name, which USER_INFO_10 does.
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371010(v=vs.85).aspx