Tru64 SSH2 umask problemٍٍ

[Osama Ahmed]

Hi,
I have a TruCluster system (5.1B PK5)where files uploaded to using sftp. The file uploaded did not get the umask value of the user account used to upload the files. The uploaded files always takes
permissions 600 !! It looks like a limitation to the SSH2 Server on the Tru64 machine.

Anyone had any experience with SSH2, any work arounds there to solve this problem ?

We can't use OpenSSH as some Cluster utilities/Advfs Utilities did not work with OpenSSH.

Please Help

[Ivan Ferreira]

If sftp is enabled, probably you can use scp. Using scp -p may help.

[Osama Ahmed]

Ivan,
I can't control the upload process as another company. They just use sftp.

My question:
- Is sftp login make use of the user profile ? i.e: Can I execute a shell script in user profile upon login to change the ownership ?

Thanks

[Ivan Ferreira]

No, you cant. The sftp command is does not have too many options. I suggested scp because normally, ssh, scp ans sftp are available if you open port 22 on the firewall.

[Vladimir Fabecic]

Hello
Are you using advanced security?
In that case default umask should be 077, I think.

[Ann Majeske]

Why don't you just create a script to change the file permissions the way you want and set it to run periodically from cron?

[Osama Ahmed]

The uploaded files got picked by a running process.

The smallest period cron can handle is every min, and the running process can try to pick the file while the cron is just waiting to be executed next min.

This will make the process miss the file because of its permissions.

I am using enhanced security. Is SSH use the default umask of enhanced security ? If yes, Can I change the default umask of enhanced securty, to let SSH use it and solve my problem ?

Thanks

[Vladimir Fabecic]

Osama
sftp does not execute /etc/profile (where umask is defined). Your problem is caused by advanced security, not SSH2.
I think that only workaround would some script that runs in background.
Maybe someone has better idea.
Regards

[Osama Ahmed]

Vladimir,
thanks a lot. My question now is:

- Is there anyway one can change default umask of enhanced security ? If so, How ?

[Vladimir Fabecic · Accepted solution]

Osama
look this:
http://unix.derkeiler.com/Mailing-Lists/Tru64-UNIX-Managers/2005-07/0057.html

[Osama Ahmed]

Vladimir,
Thanks a lot. There is no way to change the default file permissions of Enhanced security environment.

scp will be the solution in this case.

Thanks

[Adam Garsha]

I was the guy that posted to tru64 managers list.

FYI, I ended up building an openssh daemon using the sftplogging and chroot patches... works great and, overall, I have better compatibility with all my other *NIXes since arguably openssh is the defacto/superior SSH implementation.

Caution... if you install openssh, take care to not disturb your ssh.com installation (i.e. make use of configure flags to put the install into a safe place away from the default SSH.com install package); otherwise, you could run into problems at your next patch session.

Also, once you roll-your-own... you have to be vigilent about upgrading to ensure security.

So, there are pros and cons... but having the same SSH everywhere was worth it for us.

[Adam Garsha]

I forgot to include the link to the sftplogging patch (allows umask control):

http://sftplogging.sourceforge.net/

[Kapil Jha]

Hey
to change permission every sec u can run a script which will change permission mucah faster

while true
do
chmod 660 path
done

This may help if u cant use scp -p.
Thanks