Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Disallow writing of broken .acl files #1400
If the user attempts to put/post an .acl file using the wrong content-type or if they have a syntax error in the .acl, the user then loses control of the .acl and whatever it points to. Only a server admin can fix the broken .acl, the user can't edit or delete it.
I think a minimum fix is that the server should cowardly refuse to write an .acl file that has broken syntax or the wrong content-type - allowing users to do this has no benefits and quite terrible consequences - it guarantees that no one except the server admin can access the .acl or the resources it points to.
This is not quite correct. Anyone with access to the file system should be able to edit it or delete.
This should actually be all users. The idea of a centralized server admin should be something we would like to make less common, both in thought process, and in reality
This is a practical point as well as theoretical. For most of my Pods I will have access to the file system. Using solid any other way, is for me, a poor mans solid, and IMHO not really giving too much advantage
This can be applied to both the single user and multi user server. For example you can give each solid user a unix user id and login via SSH. This has a number of advantages including allowing you to set a file quota. I do this with node solid server today, and I would hate to use a pod that didnt offer that feature/service at some point. It would be the equivalent of getting a VPS and only access via FTP