On Tue, 9 May 2000, Sami Lehtinen wrote:
> : It seems to me it would be much cleaner (and easier ;-)) to modify
> : the servers behavior to ignore .cshrc when subsystem-sftp is
> : executed. Can you recommend a way to do this (or are we even allowed
> : to do this?)? Is SSH working on a fix for this problem?
>
> Aargh, I *hate* this kind of kludges.
>
> sh, bash and zsh (I presume ksh also behaves like this) don't source
> their rc-files, if they are non-interactive (ie. executing command).
>
> tcsh (atleast, and very probably csh (I can't verify this right this
> minute)) source their rc-files even if non-interactive. If they are
> given the argument "-f", they won't read the dot-rc files at startup.
Yep, csh does this as well...
> Suggestions? Should I check if the shell is "*csh" and give the
> argument "-f", if executing a command?
That was exactly what I was thinking. I tried "csh -f" wrapper
script to call from sshd2_config, but apparently the damage is done
before the sftp-server process is called...
A patch for this would be _much_ appreciated...
--ray
-----------------------------------------------------------------
Ray Daoud Computing Center
Security Analyst McGill University
[EMAIL PROTECTED]
-----------------------------------------------------------------
