New answers tagged file-permissions
use: Add-NTFSAccess -Path 'C:\MyFolder' -Account BUILTIN\IIS_IUSRS -AccessRights FullControl or just Add-NTFSAccess -Path 'C:\MyFolder' -Account IIS_IUSRS -AccessRights FullControl IIS_IUSRS is a special internal group that you shouldn't/can't prefix with the computer or domain name.
Add default ACLs, like this: default:user::rwx default:group::rwx default:other::--- Default ACLs are applied on new files and directories under the affected directory. You can use the following command to accomplish this: setfacl -dm u::rwx,g::rwx,m::rwx,o::0 /home/myuser
you can use command option in authorized_keys(*) of destination user to restrict acces. e.g. keys looks like: command="/bin/ls -l /foo/bar.txt" ssh-rsa AAB.... command="/bin/df -Ph " ssh-rsa AAC.... this means each command is access via its own key, but all df can share the same key. (*) see man 5 authorized_keys
The issue is not write access on /var/repo - I believe from the errors you've copied/pasted that this is set up correctly and probably always was. The issue is a lack of write permissions on /var/www. By following the instructions you've linked to what you've set up is a script that automatically takes the files you push to the git repository on the server ...
Since you've said in the comments that users push to git via their username@server, you need to make sure all git users have read and write permissions to the repository. Add all users to a common group, called, say, git-users. groupadd git-users Now add each git user to the group: usermod -a -G git-users <username> Now, change the ownership ...
No there isn't, but you shouldn't be assigning individual users to shared folders anyway. Use groups and then add users to those groups. Then you won't need to keep propagating permission changes and also keeps you from having a disaster of ACEs in your ACLs.
[EDIT] Yes I believe it is possible, but I also believe not with openssh: Here is how I chroot sftp using openssh: I put sftp users in a special group sftponly which is identified in the sshd_config file. I make sure sftp users have no shell (so they can't log in with ssh) and use the .%h environment variable to force them into a sftp chroot subdir named ...
Rightclick on Notepad and Start as administrator. That should help.
Notepad doesn't launch with elevated permissions by default, so you have to run notepad as administrator and then open the file using the file open dialog before you can save changes back to the original file.
I found an answer to my question over at unix.stackexchange.com. The idea is to use umask and run the commands in round brackets to execute it in a subshell, so umask doesn't affect the rest of the script. ( umask 077; openssl rsa -in secure.key -out insecure.key )
Probably you have project moved from apache-2.2 to apache-2.4. Since v2.2 some changes have been introduced to the config files syntax, especially with access definitions. While apache before 2.4 have had the next syntax Order allow,deny Allow from all the 2.4+ versions have the next syntax Require all granted Please read carefully notices about ...
The usual reason I've seen for this problem is that you create the files so they are owned by you (the user that you are logged in as). You can access the files locally because you own them. When you try to access them remotely, they are accessed by user "apache" or whatever user your web server runs as. Change the permissions so that the web server can ...
Top 50 recent answers are included