X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-0.3 required=5.0	tests=AWL,BAYES_05,RCVD_IN_DNSWL_NONE
X-Spam-Check-By: sourceware.org
Message-ID: <4C447CF5.30706@x-ray.at>
Date: Mon, 19 Jul 2010 18:27:33 +0200
From: Reini Urban <rurban AT x-ray DOT at>
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.10) Gecko/20100504 SeaMonkey/2.0.5
MIME-Version: 1.0
To: Victor Wagner <vitus AT wagner DOT pp DOT ru>
CC: Cygwin List <cygwin AT cygwin DOT com>
Subject: FW: cygwin sshd ideas (WAS: catdoc)
References: <4C3EB10A DOT 6030402 AT gmx DOT de> <AANLkTimAIy8zMSLzWEL7j4tzU_9yIz1Zu0YdPhWPlH10 AT mail DOT gmail DOT com> <4C3EBA81 DOT 1090101 AT gmx DOT de> <AANLkTin7VJD-ZrWPSs23NgA8cmzSJlYmvaR4tESC7bW3 AT mail DOT gmail DOT com> <AANLkTilFEvLWY9HkbiG3Q6OTJ6IZq-Yc-Wxtsl_YJey5 AT mail DOT gmail DOT com> <20100716132544 DOT GB28127 AT wagner DOT pp DOT ru> <AANLkTimmaMQfRzeWxh_oRBtEEt-TE6DLQkfPyLM81YXB AT mail DOT gmail DOT com> <20100719113637 DOT GA13480 AT wagner DOT pp DOT ru>
In-Reply-To: <20100719113637.GA13480@wagner.pp.ru>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

[CC:cygwin added]

Victor Wagner schrieb:
> BTW, concerning cygwin users. Do you know of anybody working on
> cygwin-specific sshd patches?

Yes, Corinna Vinschen is.

> We use cygwin sshd on our win32 build macines, because we need
> to have compatible agent forwarding on all systems and are dissatisfied
> with kind of win32 console session it gives.
>
> For instance changes in the environment, made though control panel, do
> not affect any newly created session unless sshd is restarted.
> User specific settings, made via control panel are not applied at all.

Interesting idea. Normally you would send a kill -1 signal to sshd to 
re-read the configuration, even if it's the registry where it reads the 
changed ENV vars.
I forwarded it to the cygwin list.

> Microsoft telnetd does much better job.
>
> But what makes me wonder  there is no attempt in the sshd code to use
> win32 specific way to create user session.

There is. All this is hidden in the cygwin1.dll
There is scary pure win32 code to manage user sessions.
-- 
Reini Urban


--
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