[scponly] Environment variables
Ryan J Ollos
ryno at apl.washington.edu
Wed May 23 03:48:59 EDT 2007
Hi Kaleb,
Thanks a lot for the reply.
I have a Red Hat EL 4 system with openssh-3.9p1-8. I would rather not alter
the built-in packages, so maybe the best solution is to build a specific
instance of openssh and have it listen on a different port. I also don't
want the environmental variables to apply to every ssh session, and if I add
them to sshd_config, it seems like they would certainly apply to every ssh
session. What do you think?
Also, could you clarify for me ... From what I have read, when using a
chroot jail, I will need the install location of scponlyc to be within the
chroot directory. Is this correct?
- Ryan
-----Original Message-----
From: Kaleb Pederson [mailto:kibab at icehouse.net]
Sent: Tuesday, May 22, 2007 9:52 PM
To: scponly at lists.ccs.neu.edu
Cc: Ryan J Ollos
Subject: Re: [scponly] Environment variables
Hi Ryan,
These environment variables are set by SSH when you connect to it, thus they
exist and are queryied by scponly and then passed to the sftp-server. They
are configured by changing your sshd_config file after installing the
sftplogging patch that you mentioned below.
Let us know if you still have questions.
Thanks.
--Kaleb
On Wednesday 23 May 2007, Ryan J Ollos wrote:
[snip]
> My question is ... how do I set the environment variables:
> SFTP_UMASK, SFTP_PERMIT_CHMOD, SFTP_PERMIT_CHOWN, SFTP_LOG_LEVEL, and
> SFTP_LOG_FACILITY?
>
> According to what I have read online, it appears that the only way to
> set these is to recompile OpenSSH after applying a patch ... but I'm
> not even sure how to set the variables after doing that.
> http://sftplogging.sourceforge.net/
>
> Thanks!
>
> - Ryan
More information about the scponly
mailing list