Re: sshd, sftp & umask settings (ssh.com 2.4.0)
From: Joe Husk (joe@indiana.edu)
Date: 01/28/03
- Next message: Darren Tucker: "Re: OpenSSH3.5p1 vs. Commercial SSH 3.2"
- Previous message: William Ahern: "Re: Novice SSH Question"
- In reply to: Richard E. Silverman: "Re: sshd, sftp & umask settings (ssh.com 2.4.0)"
- Next in thread: Richard E. Silverman: "Re: sshd, sftp & umask settings (ssh.com 2.4.0)"
- Reply: Richard E. Silverman: "Re: sshd, sftp & umask settings (ssh.com 2.4.0)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Joe Husk <joe@indiana.edu> Date: Tue, 28 Jan 2003 16:49:23 -0500
Would it be dangerous to have:
ENV=/etc/profile
in a ~/.ssh/environment file?
-joe
In article <m1liswefc82.fsf@syrinx.oankali.net>, Richard E. Silverman
<slade@shore.net> wrote:
> >>>>> "JH" == Joe Husk <joe@indiana.edu> writes:
>
> JH> If a non-interactive, non-login shell doesn't source any startup
> JH> files how can you set an environment variable?
>
> Again, if you _read_the_man_page_, you will see I am talking about bash
> looking at *its* environment when *it* starts -- not variables it sets for
> you and its *children* when reading startup files. So if the SSH
> implementation you're using supports it, you can set ENV or BASH_ENV
> appropriately. SSH2 has number of mechanisms for this:
> {/etc,~/.ssh}/environment files, the environment= public-key option, etc.
- Next message: Darren Tucker: "Re: OpenSSH3.5p1 vs. Commercial SSH 3.2"
- Previous message: William Ahern: "Re: Novice SSH Question"
- In reply to: Richard E. Silverman: "Re: sshd, sftp & umask settings (ssh.com 2.4.0)"
- Next in thread: Richard E. Silverman: "Re: sshd, sftp & umask settings (ssh.com 2.4.0)"
- Reply: Richard E. Silverman: "Re: sshd, sftp & umask settings (ssh.com 2.4.0)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|