Follow-up Comment #3, sr #105838 (project administration): Hi,
I have: 1) sent a message to OpenSSH project: http://marc.info/?l=openssh-unix-dev&m=117745562123264&w=4 (no answer [yet]) 2) I manage to change all directories permissions using the following procedure: mkdir TSP_DA scp -r [EMAIL PROTECTED]:/releases/tsp TSP_DA mkdir TSP_DA_dironly cd TSP_DA find . -type d -exec mkdir ../TSP_DA_dironly/{} \; cd ../TSP_DA_dironly chmod -R g+ws tsp/ scp -rp tsp/ [EMAIL PROTECTED]:/releases Then all permissions seems to be "right" for now. During my review of those permissions issue I noticed that symlinks created using sftp "symlink" command display "svusers" group instead of "tsp" (project group) you may check this in tsp download area there: sftp> pwd Remote working directory: /srv/download/tsp/prebuilt/windows sftp> ls -l lrwxrwxrwx 1 erk svusers 72 Apr 24 22:04 tsp-0.8.2-Windows.exe lrwxrwxrwx 1 erk svusers 76 Apr 24 22:04 tsp-0.8.2-Windows.exe.sig sftp> thoses files are symlinks to: sftp> pwd Remote working directory: /srv/download/tsp/tsp-0.8.x/tsp-0.8.2/prebuilt/windows sftp> ls -la drwxrwsr-x 2 erk tsp 4096 Apr 24 22:13 . drwxrwsr-x 3 erk tsp 4096 Apr 24 22:13 .. -rwxr-xr-x 1 erk tsp 5003981 Nov 29 08:42 tsp-0.8.2-Windows.exe -rwxr-xr-x 1 erk tsp 65 Nov 29 08:42 tsp-0.8.2-Windows.exe.sig sftp> It is not a "real" issue since even if group is not the appropriate one the symlink work as expected. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/support/?105838> _______________________________________________ Message posté via/par Savannah http://savannah.gnu.org/
