From: Charles Russell <worwor@bellsouth.net>
To: cygwin@cygwin.com
Subject: Re: Installing sshd with option --type manual
Date: Sat, 06 May 2017 17:28:00 -0000 [thread overview]
Message-ID: <d5c547f3-fd44-244e-51f0-5eeb5e4eafd3@bellsouth.net> (raw)
In-Reply-To: <odvo8o$3ib$1@blaine.gmane.org>
On 4/28/2017 10:48 AM, Charles Russell wrote:
> Starting from a default installation of sshd that was working properly,
> I tried uninstalling sshd with cygrunsrv and reinstalling with --type
> manual.
>
> (cygrunsrv --install sshd --path /usr/sbin/sshd.exe --type manual)
>
> After rebooting I cannot start sshd with cygrunsrv. Instead, I get
> message "Error starting a service: Query service status: Win32 Error 1062"
>
> Is it practical to use "--type manual" with sshd, or are its security
> restrictions too tight for this kind of installation? My intent was to
> have sshd off by default, but available when I need it, with current
> status easily seen with ps.
>
> Is there an easy fixup for my broken sshd, or should I rerun
> ssh-host-config?
>
>
With no response to this message, I reran ssh-host-config, which fixed
the broken sshd and very kindly did not even require me to re-enter the
pubkeys. It would be nice if it also offered an option for manual start.
Inspecting the ssh-host-config script, I see that installing the server
requires some configuration options that I don't understand. I'm now
using the firewall to disable the server by default, though "net start
sshd" and "net stop sshd" would have been more convenient.
--
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
prev parent reply other threads:[~2017-05-06 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 2:35 Charles Russell
2017-05-04 20:31 ` Fran Litterio
2017-05-07 0:18 ` Charles Russell
2017-05-07 0:25 ` Charles Russell
2017-05-07 3:27 ` Charles Russell
2017-05-10 5:31 ` Charles Russell
2017-05-10 18:01 ` Brian Inglis
2017-05-06 17:28 ` Charles Russell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5c547f3-fd44-244e-51f0-5eeb5e4eafd3@bellsouth.net \
--to=worwor@bellsouth.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).