file permission set to 000 (chmod 000) only during transmission (scp/sftp)

file permission set to 000 (chmod 000) only during transmission (scp/sftp)

Post by Dirk Wiedenbau » Thu, 28 Oct 2004 22:42:23



Hi all.

We are using two differen SSH Versions
- SSH Secure Shell 2.3.0 (non-commercial version) on
sparc-sun-solaris2.7
- OpenSSH_3.7.1p2, SSH protocols 1.5/2.0, OpenSSL 0.9.7c 30 Sep 2003
--> Solaris 2.8

When transfering files with "SSH Secure Shell 2.3.0" the file
permission is set to 000 (chmod 000). As soon as the transmission has
finished the permission of the file is set to the default value (e.g.
640).

We now have installed "OpenSSH_3.7.1p2" . The behaviour of the file
transfer has changed . The file permission  (e.g. 640) is set already
at the beginning of the transmission.

We liked the transmission behaviour of the older version (SSH Secure
Shell 2.3.0). Does anybody knows what to change on "OpenSSH_3.7.1ps"
so it behavious the same as  "SSH Secure Shell 2.3.0"?

Many thanks.
Dirk

 
 
 

1. smbfs: "----------" (000) permissions

redhat 5?  get the updated smbfs from the errata page at www.redhat.com.

--
Frank Sweetser rasmusin at wpi.edu fsweetser at blee.net | PGP key available
paramount.res.wpi.net RH 5.0 kernel 2.0.33/2.1.89p1 i586 | at public servers
Coach: Can I draw you a beer, Norm?
Norm:  No, I know what they look like.  Just pour me one.
                -- Cheers, No Help Wanted

2. Help with Trident9880 Blade 3D chipset

3. Converting the NUL byte (\000) in a file to another value---how?

4. How to Control a Dot Matrix Printer

5. kernel: [000] kernel-interface.c (init_module) - dmaalloc() failed.

6. linux cant find my hd!

7. OpenLDAP performance problemns with 1.500.000 entries?

8. Please help with cube installation.

9. Fix for reboot not resetting NE*000?

10. NE*000 Interface Specs.

11. ipchains : expire time is 715 000 minutes !

12. Recovering domains from an E10,000

13. NE*000 Ether probing problem