It depends on your server. I would say that most ignore the umask. I do not know why x is being set.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- honzas7
executable permission for all uploaded files
Hi all,
I have umask set to 002 in /etc/pam.d/common-session (session optional pam_umask.so umask=002), when I connect using scp and check the umask in winscp terminal I get 002, but all uploaded files have executable (x) permission added for both user and group. Is it default behaviour to add the x permission to all files uploaded from windows using scp?
I'm aware that I can change the permission assigned to uploaded files/directories in winscp settings, but I'm just curious why it doesn't follow the umask settings?
Thanks for response
I have umask set to 002 in /etc/pam.d/common-session (session optional pam_umask.so umask=002), when I connect using scp and check the umask in winscp terminal I get 002, but all uploaded files have executable (x) permission added for both user and group. Is it default behaviour to add the x permission to all files uploaded from windows using scp?
I'm aware that I can change the permission assigned to uploaded files/directories in winscp settings, but I'm just curious why it doesn't follow the umask settings?
Thanks for response