public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd fails to start: logon failure
Date: Thu, 14 Feb 2013 23:51:00 -0000	[thread overview]
Message-ID: <511D7885.8080401@cygwin.com> (raw)
In-Reply-To: <511D602E.805@cs.utoronto.ca>

On 2/14/2013 5:07 PM, Ryan Johnson wrote:
> On 14/02/2013 4:19 PM, Larry Hall (Cygwin) wrote:
>> On 2/14/2013 4:02 PM, Ryan Johnson wrote:
>>> On 14/02/2013 3:52 PM, marco atzeri wrote:
>>>> On 2/14/2013 9:43 PM, Ryan Johnson wrote:
>>>>> Hi all,
>>>>>
>>>>> I tried to ssh to my cygwin box today and was unable to connect. It
>>>>> seems the sshd service can no longer run, for reasons that mystify me:
>>>>>> # net start sshd
>>>>>> System error 1069 has occurred.
>>>>>>
>>>>>> The service did not start due to a logon failure.
>>>>>
>>>>> I wasn't aware of having changed anything; would it be advisable to just
>>>>> reinstall sshd from setup.exe and/or sshd_host_config, or is there some
>>>>> simple troubleshooting I might do?
>>>>
>>>> reinstall is not the way.
>>>> Likely something reset the cyg_server privileges.
>>>> Try to re-enable them with
>>>>
>>>> editrights -u cyg_server -a SeAssignPrimaryTokenPrivilege
>>>> editrights -u cyg_server -a SeCreateTokenPrivilege
>>>> editrights -u cyg_server -a SeTcbPrivilege
>>>> editrights -u cyg_server -a SeServiceLogonRight
>>>> editrights -u cyg_server -a SeIncreaseQuotaPrivilege
>>> No luck, the same error still occurs. However, now that you mention it, I
>>> did play with cygserver settings while trying to install pgsql a while back.
>>>
>>> Is there a way to view the privileges to see what I may have broken?
>>
>> $ editrights -u cyg_server -l
>> SeAssignPrimaryTokenPrivilege
>> SeCreateTokenPrivilege
>> SeTcbPrivilege
>> SeServiceLogonRight
>> SeDenyRemoteInteractiveLogonRight
> Mine has all those, plus SeIncreaseQuotaPrivilege (possibly thanks to the
> above from Marco).
>
> It seems that I managed to de-configure sshd somehow. There's no sshd_config
> in /etc/ (just the skeleton in /etc/defaults/), and sshd-host-config doesn't
> seem to exist, either. So, I blew away the sshd and cygrunsrv services and
> their associated users and re-ran ssh-host-config. All is well now... except
> that now an enormous ascii art hippo greets me at login. Ick.

Just be glad the hippo isn't flying! ;-)

Or you could change/remove /etc/motd.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

      reply	other threads:[~2013-02-14 23:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 20:43 Ryan Johnson
2013-02-14 20:53 ` marco atzeri
2013-02-14 21:02   ` Ryan Johnson
2013-02-14 21:19     ` Larry Hall (Cygwin)
2013-02-14 22:07       ` Ryan Johnson
2013-02-14 23:51         ` Larry Hall (Cygwin) [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=511D7885.8080401@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --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).