From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: openssh: privilege separation no longer supported on Cygwin? SURPRISE!
Date: Wed, 31 May 2017 14:46:00 -0000 [thread overview]
Message-ID: <28f7eeae-ed40-9837-53bc-d2d6a33ad5a7@gmail.com> (raw)
In-Reply-To: <38be07babbfc69d5ccea67afe6f92794@smtp-cloud2.xs4all.net>
On 5/31/2017 5:37 AM, Houder wrote:
> On Tue, 30 May 2017 21:28:41, "Larry Hall (Cygwin)" wrote:
>
> [snip]
>> Cygwin's link to the Windows user ID is through the UID/SID mapping. In
>> your case, you're apparently using /etc/passwd and so that's where the
>> mapping happens. You can map the UID of a Cygwin user to any valid Windows
>> SID by editing the SID as you did. This doesn't change how things look in
>> the Cygwin environment (i.e. the UID and user name are still the same) but
>> it does make a difference to Windows. So the fact that you can change the
>> SID for the 'sshd' user and still get it to run is not all that surprising,
>> assuming that the new Windows SID that you're using as 'sshd' now has at
>> least similar permissions. Of course, if you remove Cygwin's understanding
>> of 'sshd' so that it can't do the mapping of UID to SID or even have a
>> valid UID, then subsequent problems are not unexpected.
>
> Hi Larry,
>
> Thanks for your reply! Discussion!
>
> First of all, I do not pretend to know Windows ... neither do I pretend that I
> know more about ssh/Cygwin than Corinna does (basically, I know not very much).
>
> .. the only thing I am able to, is "observe" (and I may interpret wrong), and
> may have done "stupid" things. That is why your reply is appreciated by me.
>
> Now back to your reply:
>
> I had modified /etc/password as follows: (note the xxxx in the sid)
>
> sshd:*:1015:513:U-Seven\sshd,S-1-5-21-91509220-1575020443-2714799223-xxxx:/var/empty:/bin/false
>
> However, just now I modified it as follows:
>
> sshd:*:1015:513:U-Seven\sshd,S-1-5-21-xxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxx:/var/empty:/bin/false
>
> (again changed the sshd service into 'automatic'), and rebooted the system.
>
> After system reboot, an elevated shell is started ...
> (the ampersand sign at the end of the prompt indicates it is an elevated shell)
All of this talk of /etc/passwd leads me to point you to
https://cygwin.com/cygwin-ug-net/ntsec.html.
--
cyg Simple
--
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
next prev parent reply other threads:[~2017-05-31 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 6:40 openssh: privilege separation no longer supported on Cygwin? Houder
2017-05-29 9:22 ` Marco Atzeri
2017-05-29 11:39 ` Houder
2017-05-29 11:44 ` openssh: privilege separation no longer supported on Cygwin? -- example only Houder
2017-05-29 14:29 ` openssh: privilege separation no longer supported on Cygwin? Houder
2017-05-29 17:45 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! Houder
2017-05-29 20:30 ` Andrey Repin
2017-05-30 3:49 ` Houder
2017-05-30 16:16 ` Houder
2017-05-31 4:58 ` Larry Hall (Cygwin)
2017-05-31 10:51 ` Houder
2017-05-31 14:46 ` cyg Simple [this message]
2017-05-31 14:57 ` Houder
2017-05-31 14:59 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! -- minor correction Houder
2017-05-31 16:34 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! cyg Simple
2017-05-31 19:52 ` Houder
2017-05-31 20:16 ` cyg Simple
2017-06-01 2:27 ` Larry Hall (Cygwin)
2017-05-31 20:20 ` openssh: privilege separation no longer supported on Cygwin? Marco Atzeri
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=28f7eeae-ed40-9837-53bc-d2d6a33ad5a7@gmail.com \
--to=cygsimple@gmail.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).