This is the mail archive of the
cygwin
mailing list for the Cygwin project.
FW: cygwin sshd ideas (WAS: catdoc)
- From: Reini Urban <rurban at x-ray dot at>
- To: Victor Wagner <vitus at wagner dot pp dot ru>
- Cc: Cygwin List <cygwin at cygwin dot com>
- Date: Mon, 19 Jul 2010 18:27:33 +0200
- Subject: FW: cygwin sshd ideas (WAS: catdoc)
- References: <4C3EB10A.6030402@gmx.de> <AANLkTimAIy8zMSLzWEL7j4tzU_9yIz1Zu0YdPhWPlH10@mail.gmail.com> <4C3EBA81.1090101@gmx.de> <AANLkTin7VJD-ZrWPSs23NgA8cmzSJlYmvaR4tESC7bW3@mail.gmail.com> <AANLkTilFEvLWY9HkbiG3Q6OTJ6IZq-Yc-Wxtsl_YJey5@mail.gmail.com> <20100716132544.GB28127@wagner.pp.ru> <AANLkTimmaMQfRzeWxh_oRBtEEt-TE6DLQkfPyLM81YXB@mail.gmail.com> <20100719113637.GA13480@wagner.pp.ru>
- Reply-to: Cygwin 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