subject:"RE\: sshd in Windows 2003 server"

Re: sshd in Windows 2003 server

2004-12-10 Thread Larry Hall

At 01:10 PM 12/10/2004, you wrote:
>On Fri, Dec 10, 2004 at 12:40:37PM -0500, Larry Hall wrote:
>>At 12:34 PM 12/10/2004, you wrote:
>>>On Fri, 10 Dec 2004, Brian Dessent wrote:
>>>
 Larry Hall wrote:
 >
 > The shortcut for all of that process is to run the below:
 >
 > mount -f -s -b "/bin" 
 > "/usr/bin"
 > mount -f -s -b "/lib" 
 > "/usr/lib"
 > mount -f -s -b "" "/"
 >
 > FWIW, following the reporting guidelines at 
 > 
 > would have given the list this information in your initial post.  In 
 > other
 > words, there's good stuff at this page. :-)

 hmm... what if there was a simple shell script added to base-files, such
 as "mksysmounts" (and corresponding "mkusermounts" too I suppose) that
 would change any system mounts to user mounts, and vice versa.  (Or
 perhaps a single script with several options.)  Then the response to "I
 installed 'For me only'" would be "just run mksysmounts" instead of
 "reinstall" or "modify these paths as appropriate and run these
 commands".
>>>
>>>Good idea.  I'd call the scripts "remount_as_system" and "remount_as_user"
>>>or something...  And I would also use the
>>>
>>>eval "`mount -m | sed ...`"
>>>
>>>trick that I posted earlier, instead of hard-coding the paths into the
>>>scripts.
>>
>>
>>I have no problem with this but if we're offering suggestions on how to 
>>fix the actual problem, then I'd go to the source and change the install 
>>scripts or maybe even 'cygrunsrv' to provide a warning and/or 'fix'.  
>>That should reduce the number of people having problems running service
>>to only those that don't have permission to do so, in which case we can't 
>>help them anyway.
>
>Maybe we should just get rid of the "install as user" option and only
>use it when absolutely necessary.  Then issue a warning at that point.

Yeah, I'd agree that it's unclear to current users what the implication 
is for installing as "Just for Me" so I don't think it should be a user
selected option.  So I think your suggestion is a step in the right 
direction.


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


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

Re: sshd in Windows 2003 server

2004-12-10 Thread Christopher Faylor

On Fri, Dec 10, 2004 at 12:40:37PM -0500, Larry Hall wrote:
>At 12:34 PM 12/10/2004, you wrote:
>>On Fri, 10 Dec 2004, Brian Dessent wrote:
>>
>>> Larry Hall wrote:
>>> >
>>> > The shortcut for all of that process is to run the below:
>>> >
>>> > mount -f -s -b "/bin" 
>>> > "/usr/bin"
>>> > mount -f -s -b "/lib" 
>>> > "/usr/lib"
>>> > mount -f -s -b "" "/"
>>> >
>>> > FWIW, following the reporting guidelines at 
>>> > 
>>> > would have given the list this information in your initial post.  In other
>>> > words, there's good stuff at this page. :-)
>>>
>>> hmm... what if there was a simple shell script added to base-files, such
>>> as "mksysmounts" (and corresponding "mkusermounts" too I suppose) that
>>> would change any system mounts to user mounts, and vice versa.  (Or
>>> perhaps a single script with several options.)  Then the response to "I
>>> installed 'For me only'" would be "just run mksysmounts" instead of
>>> "reinstall" or "modify these paths as appropriate and run these
>>> commands".
>>
>>Good idea.  I'd call the scripts "remount_as_system" and "remount_as_user"
>>or something...  And I would also use the
>>
>>eval "`mount -m | sed ...`"
>>
>>trick that I posted earlier, instead of hard-coding the paths into the
>>scripts.
>
>
>I have no problem with this but if we're offering suggestions on how to 
>fix the actual problem, then I'd go to the source and change the install 
>scripts or maybe even 'cygrunsrv' to provide a warning and/or 'fix'.  
>That should reduce the number of people having problems running service
>to only those that don't have permission to do so, in which case we can't 
>help them anyway.

Maybe we should just get rid of the "install as user" option and only
use it when absolutely necessary.  Then issue a warning at that point.

cgf

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

Re: sshd in Windows 2003 server

2004-12-10 Thread Larry Hall

At 12:34 PM 12/10/2004, you wrote:
>On Fri, 10 Dec 2004, Brian Dessent wrote:
>
>> Larry Hall wrote:
>> >
>> > The shortcut for all of that process is to run the below:
>> >
>> > mount -f -s -b "/bin" "/usr/bin"
>> > mount -f -s -b "/lib" "/usr/lib"
>> > mount -f -s -b "" "/"
>> >
>> > FWIW, following the reporting guidelines at 
>> > 
>> > would have given the list this information in your initial post.  In other
>> > words, there's good stuff at this page. :-)
>>
>> hmm... what if there was a simple shell script added to base-files, such
>> as "mksysmounts" (and corresponding "mkusermounts" too I suppose) that
>> would change any system mounts to user mounts, and vice versa.  (Or
>> perhaps a single script with several options.)  Then the response to "I
>> installed 'For me only'" would be "just run mksysmounts" instead of
>> "reinstall" or "modify these paths as appropriate and run these
>> commands".
>
>Good idea.  I'd call the scripts "remount_as_system" and "remount_as_user"
>or something...  And I would also use the
>
>eval "`mount -m | sed ...`"
>
>trick that I posted earlier, instead of hard-coding the paths into the
>scripts.


I have no problem with this but if we're offering suggestions on how to 
fix the actual problem, then I'd go to the source and change the install 
scripts or maybe even 'cygrunsrv' to provide a warning and/or 'fix'.  
That should reduce the number of people having problems running service
to only those that don't have permission to do so, in which case we can't 
help them anyway.


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


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

Re: sshd in Windows 2003 server

2004-12-10 Thread Igor Pechtchanski

On Fri, 10 Dec 2004, Brian Dessent wrote:

> Larry Hall wrote:
> >
> > The shortcut for all of that process is to run the below:
> >
> > mount -f -s -b "/bin" "/usr/bin"
> > mount -f -s -b "/lib" "/usr/lib"
> > mount -f -s -b "" "/"
> >
> > FWIW, following the reporting guidelines at 
> > 
> > would have given the list this information in your initial post.  In other
> > words, there's good stuff at this page. :-)
>
> hmm... what if there was a simple shell script added to base-files, such
> as "mksysmounts" (and corresponding "mkusermounts" too I suppose) that
> would change any system mounts to user mounts, and vice versa.  (Or
> perhaps a single script with several options.)  Then the response to "I
> installed 'For me only'" would be "just run mksysmounts" instead of
> "reinstall" or "modify these paths as appropriate and run these
> commands".

Good idea.  I'd call the scripts "remount_as_system" and "remount_as_user"
or something...  And I would also use the

eval "`mount -m | sed ...`"

trick that I posted earlier, instead of hard-coding the paths into the
scripts.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

Re: sshd in Windows 2003 server

2004-12-10 Thread Brian Dessent

Larry Hall wrote:
> 
> The shortcut for all of that process is to run the below:
> 
> mount -f -s -b "/bin" "/usr/bin"
> mount -f -s -b "/lib" "/usr/lib"
> mount -f -s -b "" "/"
> 
> FWIW, following the reporting guidelines at 
> would have given the list this information in your initial post.  In other
> words, there's good stuff at this page. :-)

hmm... what if there was a simple shell script added to base-files, such
as "mksysmounts" (and corresponding "mkusermounts" too I suppose) that
would change any system mounts to user mounts, and vice versa.  (Or
perhaps a single script with several options.)  Then the response to "I
installed 'For me only'" would be "just run mksysmounts" instead of
"reinstall" or "modify these paths as appropriate and run these
commands".

Brian

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

Re: sshd in Windows 2003 server

2004-12-10 Thread Larry Hall

The shortcut for all of that process is to run the below:

mount -f -s -b "/bin" "/usr/bin"
mount -f -s -b "/lib" "/usr/lib"
mount -f -s -b "" "/"

FWIW, following the reporting guidelines at <http://cygwin.com/problems.html>
would have given the list this information in your initial post.  In other
words, there's good stuff at this page. :-)

But as you can see, there is more than one way to a solution. :-)

Larry

At 12:05 PM 12/10/2004, you wrote:

>Thanks Bill,
>your suggestion did the trick. It wouldn't be a bad idea to remind at 
>/usr/share/doc/Cygwin/openssh.README that sshd only works if cygwin is 
>installed for all users (which is obvious, though)
>
>That's what I did to fix it
>*delete the sshd_server
>*remove the NT service with "cygrunsrv --remove sshd"
>*Run the cygwin setup just changing "Just Me" to "All Users"
>*rerun ssh-host-config
>
>best regards
>
>William R. Knox wrote:
>
>>A usual question (sent strictly to you as I'm not sure if it is at all
>>relevant) - did you install Cygwin for All Users or for yourself only? If
>>you installed only for yourself, try reinstalling for All Users and see if
>>this clears it up (no guarantees here, so don't do anything that would
>>cause a lot of hassle for yourself based on my word alone). Good luck, and
>>feel free to forward this message to the list if this solves it for you
>>and you want to share the solution.
>>
>>Bill Knox
>>Lead Operating Systems Programmer/Analyst
>>The MITRE Corporation
>>
>>On Thu, 9 Dec 2004, daniel wrote:
>>
>> 
>>
>>>Date: Thu, 09 Dec 2004 15:36:59 +0100
>>>From: daniel <[EMAIL PROTECTED]>
>>>To: [EMAIL PROTECTED]
>>>Subject: Re: sshd in Windows 2003 server
>>>
>>>Thanks,
>>>   I actually executed ssh-host-config and chose to create the NT
>>>service and  both the sshd and sshd_server users. Everything looks
>>>exactly the same as in my WinXP succesful installation. However, on my
>>>Win2003, when I run  "cygrunsrv.exe --start sshd", I  always get
>>>immediately the 1053 error. The cygrunsrv process stays running, but the
>>>NT service appears for ever as "starting". At the Windows Event Viewer,
>>>I can only see "The CYGWIN sshd service was successfully sent a start
>>>control.", but nothing else. No file /var/log/sshd.log is not created.
>>>Is there anything else I can check?
>>>
>>>best regards
>>>
>>>//
>>>
>>>   * /From/: "Harig, Mark"
>>>   * /To/: 
>>>   * /Date/: Thu, 2 Dec 2004 10:30:22 -0500
>>>   * /Subject/: RE: sshd in Windows 2003 server
>>>
>>>
>>>
>>>Using 'openssh-host-config' is the only documented, supported
>>>approach to setting up a Cygwin openssh server.  If you follow
>>>instructions from other locations, then you need to ask for
>>>assistance at those locations.  The documentation for the Cygwin-specific
>>>openssh setup begins in /usr/share/doc/Cygwin/openssh.README.
>>>
>>>   
>>>
>>>>-Original Message-
>>>>From: daniel
>>>>Sent: Thursday, December 02, 2004 6:32 AM
>>>>To: [EMAIL PROTECTED]
>>>>Subject: sshd in Windows 2003 server
>>>>
>>>>
>>>>Hi,
>>>>   I've installed sshd succesfully a couple of time on WinXP
>>>>machines
>>>>following the instructions at
>>>>http://pigtail.net/LRP/printsrv/cygwin-sshd.html.
>>>>However, I didn' manage on a Windows 2003 server.
>>>>I always get "1053 did not start in a timely fashion" immediately on
>>>>clicking on the Windows service "start" button. I tried with both
>>>>enabling and disabling the privilege separation.
>>>>
>>>>I don't think I have to follow the instructions at
>>>>http://www.cygwin.com/ml/cygwin/2003-09/msg00977.html, since
>>>>my cygwin
>>>>version (cygwin DLL version: 1.5.12) already creates a
>>>>ssd_server user
>>>>with the privileges mentioned there.
>>>>
>>>> 
>>>--
>>>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/
>>>
>>>
>>>   
>>
>> 
>
>
>--
>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/

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


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

Re: sshd in Windows 2003 server

2004-12-10 Thread daniel

Thanks Bill,
your suggestion did the trick. It wouldn't be a bad idea to remind at 
/usr/share/doc/Cygwin/openssh.README that sshd only works if cygwin is 
installed for all users (which is obvious, though)

That's what I did to fix it
*delete the sshd_server
*remove the NT service with "cygrunsrv --remove sshd"
*Run the cygwin setup just changing "Just Me" to "All Users"
*rerun ssh-host-config
best regards
William R. Knox wrote:
A usual question (sent strictly to you as I'm not sure if it is at all
relevant) - did you install Cygwin for All Users or for yourself only? If
you installed only for yourself, try reinstalling for All Users and see if
this clears it up (no guarantees here, so don't do anything that would
cause a lot of hassle for yourself based on my word alone). Good luck, and
feel free to forward this message to the list if this solves it for you
and you want to share the solution.
Bill Knox
Lead Operating Systems Programmer/Analyst
The MITRE Corporation
On Thu, 9 Dec 2004, daniel wrote:
 

Date: Thu, 09 Dec 2004 15:36:59 +0100
From: daniel <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: sshd in Windows 2003 server
Thanks,
   I actually executed ssh-host-config and chose to create the NT
service and  both the sshd and sshd_server users. Everything looks
exactly the same as in my WinXP succesful installation. However, on my
Win2003, when I run  "cygrunsrv.exe --start sshd", I  always get
immediately the 1053 error. The cygrunsrv process stays running, but the
NT service appears for ever as "starting". At the Windows Event Viewer,
I can only see "The CYGWIN sshd service was successfully sent a start
control.", but nothing else. No file /var/log/sshd.log is not created.
Is there anything else I can check?
best regards
//
   * /From/: "Harig, Mark"
   * /To/: 
   * /Date/: Thu, 2 Dec 2004 10:30:22 -0500
   * /Subject/: RE: sshd in Windows 2003 server

Using 'openssh-host-config' is the only documented, supported
approach to setting up a Cygwin openssh server.  If you follow
instructions from other locations, then you need to ask for
assistance at those locations.  The documentation for the Cygwin-specific
openssh setup begins in /usr/share/doc/Cygwin/openssh.README.
   

-Original Message-
From: daniel
Sent: Thursday, December 02, 2004 6:32 AM
To: [EMAIL PROTECTED]
Subject: sshd in Windows 2003 server
Hi,
   I've installed sshd succesfully a couple of time on WinXP
machines
following the instructions at
http://pigtail.net/LRP/printsrv/cygwin-sshd.html.
However, I didn' manage on a Windows 2003 server.
I always get "1053 did not start in a timely fashion" immediately on
clicking on the Windows service "start" button. I tried with both
enabling and disabling the privilege separation.
I don't think I have to follow the instructions at
http://www.cygwin.com/ml/cygwin/2003-09/msg00977.html, since
my cygwin
version (cygwin DLL version: 1.5.12) already creates a
ssd_server user
with the privileges mentioned there.
 

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

 


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

Re: sshd in Windows 2003 server

2004-12-09 Thread daniel

Thanks,
   I actually executed ssh-host-config and chose to create the NT 
service and  both the sshd and sshd_server users. Everything looks 
exactly the same as in my WinXP succesful installation. However, on my 
Win2003, when I run  "cygrunsrv.exe --start sshd", I  always get 
immediately the 1053 error. The cygrunsrv process stays running, but the 
NT service appears for ever as "starting". At the Windows Event Viewer, 
I can only see "The CYGWIN sshd service was successfully sent a start 
control.", but nothing else. No file /var/log/sshd.log is not created. 
Is there anything else I can check?

best regards
//
   * /From/: "Harig, Mark"
   * /To/: 
   * /Date/: Thu, 2 Dec 2004 10:30:22 -0500
   * /Subject/: RE: sshd in Windows 2003 server

Using 'openssh-host-config' is the only documented, supported
approach to setting up a Cygwin openssh server.  If you follow
instructions from other locations, then you need to ask for
assistance at those locations.  The documentation for the Cygwin-specific
openssh setup begins in /usr/share/doc/Cygwin/openssh.README.
-Original Message-
From: daniel
Sent: Thursday, December 02, 2004 6:32 AM
To: [EMAIL PROTECTED]
Subject: sshd in Windows 2003 server
Hi,
I've installed sshd succesfully a couple of time on WinXP 
machines 
following the instructions at 
http://pigtail.net/LRP/printsrv/cygwin-sshd.html.
However, I didn' manage on a Windows 2003 server. 
I always get "1053 did not start in a timely fashion" immediately on 
clicking on the Windows service "start" button. I tried with both 
enabling and disabling the privilege separation.

I don't think I have to follow the instructions at 
http://www.cygwin.com/ml/cygwin/2003-09/msg00977.html, since 
my cygwin 
version (cygwin DLL version: 1.5.12) already creates a 
ssd_server user 
with the privileges mentioned there.


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

RE: sshd in Windows 2003 server

2004-12-02 Thread Harig, Mark



> -Original Message-
> From: daniel
> Sent: Thursday, December 02, 2004 6:32 AM
> To: [EMAIL PROTECTED]
> Subject: sshd in Windows 2003 server
> 
> 
> Hi,
> I've installed sshd succesfully a couple of time on WinXP 
> machines 
> following the instructions at 
> http://pigtail.net/LRP/printsrv/cygwin-sshd.html.
> However, I didn' manage on a Windows 2003 server. 
> I always get "1053 did not start in a timely fashion" immediately on 
> clicking on the Windows service "start" button. I tried with both 
> enabling and disabling the privilege separation.
> 
> I don't think I have to follow the instructions at 
> http://www.cygwin.com/ml/cygwin/2003-09/msg00977.html, since 
> my cygwin 
> version (cygwin DLL version: 1.5.12) already creates a 
> ssd_server user 
> with the privileges mentioned there.
> 

Using 'openssh-host-config' is the only documented, supported
approach to setting up a Cygwin openssh server.  If you follow
instructions from other locations, then you need to ask for
assistance at those locations.  The documentation for the Cygwin-specific
openssh setup begins in /usr/share/doc/Cygwin/openssh.README.

---

(Please do not reply to me, instead keep all replies on this list.
Please do not include my email address in any replies.)

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

Re: sshd in Windows 2003 server

Re: sshd in Windows 2003 server

Re: sshd in Windows 2003 server

Re: sshd in Windows 2003 server

Re: sshd in Windows 2003 server

Re: sshd in Windows 2003 server

Re: sshd in Windows 2003 server

Re: sshd in Windows 2003 server

RE: sshd in Windows 2003 server

9 matches

Site Navigation

Mail list logo

Footer information