sftp and trusted systems

[Mark Zurl]

I have an 8 node metrocluster (cluster with SRDF). Recently, I turned on auditing ("Trusted Systems", C2 Security) on all the nodes, and one important job failed. There was no other fallout.

The owners of the job stated that after I implemented Trusted System, the umask of their sftp job changed from 644 to 600. In other words, they sftp from a Windows machine to one node in my cluster, and after implementing C2, the dataset transferred comes across with a default permission of 600 instead of the usual 644. This caused the job to fail.

When I implemented C2, I did not boot any cluster node, or stop/restart the secure shell daemon.

Does anyone know how the umask for incoming sftp's could have changed in this situation? I looked around and could not find a connection. Any feedback would be appreciated.

[Court Campbell]

check out SftpUmask in sshd_config. See what it is set to, change it if needed, then restart secsh. If that fails then refer to this thread. It may help.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1308248

[Mark Zurl]

I was aware of the umask configurable in sshd_config, but I did not modify it, or stop/start the secsh daemon to pick up any change. Also, implementing Trusted System does not modify this configurable.

[Mark Zurl]

Closing thread due to lack of response from user community. This indicates what I suspected and answers my question by default. My question was if anyone else had found a connection between trusted systems and sftp umask, and the lack of response indicates there probably is none, which is what I had thought. Thanks for allowing me to post this question on the forum.