X-Spam-Check-By: sourceware.org Message-ID: <31b7d2790611151525q7c69b099uaa790633a6539ca9@mail.gmail.com> Date: Wed, 15 Nov 2006 23:25:27 +0000 From: "DePriest, Jason R." To: cygwin AT cygwin DOT com Subject: Re: Windows environment variables in ssh sessions with privilege seperation In-Reply-To: <1163631780.4704.66.camel@Ruksana.schrodinger.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1163631780 DOT 4704 DOT 66 DOT camel AT Ruksana DOT schrodinger DOT com> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 11/15/06, Sean Morgan wrote: > I have cygwin sshd installed using privilege separation but find that > when connected via ssh that neither the windows system nor user > variables are present in the bash shell as they are when cygwin is run > in a command shell from the Windows desktop. I always add the environment variables I want an SSH shell to have when I install it. However, if you are using the ssh-config-host script, that may not be as easy (I cannot remember and since it is already installed, I don't want to run it again as it might hose something up). You can however add the environment variables you want to the Windows registry directly. Basically, look in HKLM\SYSTEM\CurrentControlSet\Services\\Parameters\Environment\ Create REG_SZ values with the names of the environment variable you want to set and make the value data what you want it set to. For example, I usually end up with: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sshd\Parameters\Environment] "CYGWIN"="TTY NTSEC SMBNTSEC BINMODE CODEPAGE:OEM" "TEMP"="/tmp" "TMP"="/tmp" HTH -Jason -- + + + NO CARRIER -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/