X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0	tests=BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=google.com; s=20120113;        h=message-id:date:from:user-agent:mime-version:to:subject         :content-type:content-transfer-encoding:x-gm-message-state;        bh=DBNb697E3g/fmJZrb+VlIirh3MUT1tsfu1XhMR3W7FQ=;        b=QR9j4jSmOWPB0oCl8/Vu2QVP0dHiCMVOX7/IrD696N9YLx55IrpKb2m1FsDgPwHsFS         AcEoN8eEtWfKdEITUxTz3Erj7lj68tcd06fgimBkDYrFQ1Ga6LCGlq5dMmOTrX60iH58         d1DlObfenIF+bIOylpCJh7tqK3LPx0Ps3wFf9hcwPmng07bhG+AcD4+mL4hM0z3f2VG+         T9Zeq3px5Okui4rC5qwcROSbLsaC3TtsDOc9qGNs/Xyf1icQ1j1m8lMlxNdwSi1CMiX6         keN3OjsXZMm0bZzTFrl37fQk/8PvZO4U5PltPmq/NxN3sozWpFXbaofE7l26CadmRQr5         lb0Q==
Message-ID: <505A03B1.6070409@silicondust.com>
Date: Wed, 19 Sep 2012 10:41:05 -0700
From: jafa <jafa@silicondust.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: sshd from user account - env issues
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQm70hz/L/XlYf8Q7AsQaR4wBAwVLnWqKU89ZOLCqzg505YXPXZM6ZLimEEk5xXKPVAUGj9W
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Hi,

I am setting up a build server that is controlled via ssh.

The build user account logs in automatically and runs the following on
login:
C:\cygwin\bin\bash.exe -l -i -c "/usr/sbin/sshd.exe"

Normally SSHD runs as a service - this works well, except that one of
the steps in the build process is a scripted GUI app and Windows does
not allow a service to launch and script-control GUI apps.

Running SSHD from the user account like this basically works - I can ssh
into the machine, but the env vars are not quite right.

For example, local bash:
TEMP=/tmp
temp=C:\Users\build\AppData\Local\Temp
TMP=/tmp
tmp=C:\Users\build\AppData\Local\Temp

SSH session:
temp=
TEMP=/tmp
tmp=
TMP=/tmp

(also a number of normal Windows env vars are completely missing. They
are present in bash when run on the local computer, but missing via ssh
connection even when sshd was manually run from that same bash shell)

The env vars were correct when sshd was running as a service.

Is there a config file that controls which env vars are allowed/filtered?

I had to change ownership of the sshd key files from SYSTEM to the build
user... first thought was that I missed a config file but I can't see
any other files owned by SYSTEM.

Any ideas?

Thanks,

Nick

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

