-
Notifications
You must be signed in to change notification settings - Fork 10
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
Folder create permissions for "mkdir -p" not enforced? #145
Comments
I had a look in the code, and when trying to create |
The PermissionBasedAuthorizer has access to a resourceSet where it can check if a resource exists. |
That's absurd. If they haven't archived the repo, it's entirely legitimate to create PRs. If they won't merge code fixes, it would be reasonable to submit PR against their README that point to more lively fork(s). |
Environment
CSS v4.0.1, node v12.19.1, npm v6.14.8
Description
Save this as
acl.ttl
which gives any agent read-only access to the server root, and read-write access to any contained resources:And upload it to a newly started CSS v4.0.1 instance using:
curl -v -X PUT -H 'Content-Type: text/turtle' -T acl.ttl http://localhost:3000/.acl
Now try these commands:
The first will give a 401, the second a 201. And indeed, if you then run
curl http://localhost:3000/
you will see that although the creation of/test.txt
was blocked correctly, the creation of a/nested
folder in the pod root was not prevented:However, the spec says that creating that
nested/
folder should have require Write or Append on /. Is WAC not enforced for the "mkdir -p" behaviour of creating nested folders?The text was updated successfully, but these errors were encountered: