Skip to content
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

BUG: Security API doesn't always set the FULL access rule correctly #21

Open
ferventcoder opened this issue Jun 16, 2011 · 0 comments
Open

Comments

@ferventcoder
Copy link
Member

I remember searching stackoverflow to find out why permission weren't being set right. I looked at the ACL routine in dropkick and it turned out there was a lot of things dropkick was doing that didn't really set the "full access" rule correctly (ie: bug).

In my case, my answer here was what solved my issue:

http://stackoverflow.com/questions/5935630/how-to-set-full-control-to-a-directory/6175523#6175523

** PropagationFlags.None was required in my case. I think dropkick didn't do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant