-----BEGIN PGP SIGNED MESSAGE-----
Thank you for your response...the -p switch does fix the problem. I
had combed the ssh documentation, but for some reason didn't think to
check the scp man page. My apologies for the oversight.
Thanks again -d
- --
David Talkington
Community Networking Initiative
[EMAIL PROTECTED]
217-244-1962
PGP key: http://www.prairienet.org/~dtalk/dt000823.asc
Cameron Simpson wrote:
>On Thu, Oct 26, 2000 at 08:54:24PM -0500, David Talkington wrote:
>| This was first mentioned in July, and I've seen no progress on the
>| thread. It doesn't appear that my last message on this topic reached
>| the list; I apologize if we end up with duplicates.
>|
>| I was disturbed to see that during uploads via scp from a Linux
>| workstation to a Solaris server, where the permissions on the original
>| file were 644 and the umask for the receiving user was 022, the
>| uploaded file was created 666. I uploaded a file to my public web
>| directory on the server some weeks ago, and only just now discovered
>| that it was world-writeable. I confirmed that scp was to blame by
>| repeating the upload, checking the umask and perms before the
>| transfer.
>
>Does this behaviour persist if you use the -p flag with scp?
>
>Without it I would guess (from the behaviour) that the sshd is running with a
>umask of 0. You can test this by tweaking the umask in the sshd startup file
>on the server and restarting sshd.
>
>The notion "umask for the receiving user" is pretty nebulous; such things
>are normally set during the login process via the /etc/profile file or and/or
>the user's ~/.profile file. Neither is consulted by scp.
>
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
Comment: Made with pgp4pine 1.75-6
iQEVAwUBOg3vcb1ZYOtSwT+tAQFNqggApD6q8Lmsuhj3r/cOBUoIO9b5OyBEYDfS
0X4cgkybPujK1IIpem1yTBesr9ddmusVV0BfGvWFUkits536hg5Qb8+FVLrufh7f
wpChqMFE6qQaXIwBIv2i0pxqEvlHDwp9FtgIHS7wo5LPhDtIVqeI5k/becbl9Ra7
cXCmMBn6sQe1FmoIpTtSZE6oPjN4uTpglYCoHCWQymcjiazmpe+OLSKj3yvt3D4J
0inFW6V/DFnGMkFCHm40hEnTmiTiS4Q601kS6rxQPXbbEc1taxefOFfKHyoBr/TN
Jd6S4OB8eD7CrCFqqsD/Ermz7cZKtqcPwb+dxyvXEUgp/YVBpygCBA==
=Gnya
-----END PGP SIGNATURE-----
