Added Advapi32Util accessCheck method to verify file permissions#301
Added Advapi32Util accessCheck method to verify file permissions#301dblock merged 4 commits intojava-native-access:masterfrom BusyByte:master
Conversation
There was a problem hiding this comment.
Import the structures used and change things like WinDef.DWORDByRference to just DWORDByReference.
|
This is very good. You need to add lower level tests for |
|
AccessCheck is very involved so basically I think the higher level test is the lowest level test you can get for this |
|
I am happy with whatever test that calls the API and doesn't implode. |
|
I believe I've address all your concerns. Let me know if there is anything else to look at. |
There was a problem hiding this comment.
There's an extra space after [@BusyByte] that makes it a non-link. You should also add the mappings that you added as a separate line like above.
|
I still don't see a test for |
…dated changelog markup
|
I get back invalid handle. Take a look and see if there is anything else I need to do. |
There was a problem hiding this comment.
Last thing, promise. Just check that Kernel32.INSTANCE.GetLastError() is INVALID_HANDLE or something like that. This would fail on a non-US-English system.
…s and general cleanup
|
Alright let me know how it looks now. |
|
Great, merging. |
Added Advapi32Util accessCheck method to verify file permissions
Bumps logback-classic from 1.1.7 to 1.2.0. --- updated-dependencies: - dependency-name: ch.qos.logback:logback-classic dependency-type: direct:development ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
I had contacted you on the Google Group about adding this functionality to check effective file permissions for the current user.
I've added three tests to verify the positive cases.
I couldn't think of an automated way to test the negative cases so I just manually tested those and deleted the tests for those.
Let me know if you have any questions.
Can you message me back on the Google Group when you have Maven Central updated with a new release with these changes?
Shawn