public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jarek <yaro_29@hotmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin ssh and Windows authentication
Date: Mon, 20 Jul 2015 18:59:00 -0000	[thread overview]
Message-ID: <BLU436-SMTP217DCBDBFA0EED5BC1ACFFB9E850@phx.gbl> (raw)
In-Reply-To: <1301881165.20150720013859@yandex.ru>

Hi Andrey.
So why are they not needed as your comment doesn't really explain that 
and how exactly did I screwed up my setup if I can actually access the 
server with a domain user account no problem? Perhaps it's not how it 
works but it somehow works so again would be good to know why. It's only 
domain groups that don't work. Even if I set the service account to run 
under a domain account how would this fix my problem with group access 
assuming in current setup it works for domain users but not for groups? 
Again if not the /etc/passwd or /etc/group files then what controls the 
access?

On 2015-07-20 00:38, Andrey Repin wrote:
> Greetings, Jarek!
>
>> I'm still quite new to Cygwin. I'm using the most recent version to
>> install the ssh component on Server 2012R2 member server since it
>> happened to become a requirement for certain users. The problem I have
>> is to understand how to allow access for domain groups. I read the new
>> version doesn't even need the /etc/passwd and /etc/group files any more
>> but I couldn't see any explanation as to how to allow users or groups
>> permission to ssh to the cygwin sshd server.
> Short version is that you need SSH server running under domain user.
> Which needs to be created prior to starting ssh-host-config.
>
>> Running ssh-host-config answering yes to all questions except the one for
>> using other user than the cyg_server I set up the ssh daemon. Not knowing
>> any other way I created the /etc/passwd file with $mkpasswd -l > /etc/passwd
> These files no longer need, but in your specific case, you actually just
> screwed your setup.
>
>> which dumped all local users into the file. I successfully added a domain user
>> with $mkpasswd -u [domain_user] -D [domain] >> /etc/passwd.
> That's not how it works.
>
>> This worked just fine creating the /home/[user] folder I think although
>> I haven't checked if it didn't get created earlier since I installed
>> Cygwin under that user account.  No idea though how to get this working
>> without the use of /etc/passwd file. I then created the /etc/group file
>> and added my selected domain user group to it. Unfortunately in this
>> case members of the group cannot connect via ssh. I don't know if there
>> is a way to list all users including group members with access
>> permissions. $net user lists only users. I tried $net group but this
>> seems to be limited to DCs only which I have no access to. Could someone
>> please explain how can this be set up and what tellls Cygwin who can
>> connect and who can't?
> http://cygwin.com/faq/faq.html#faq.using.sshd-in-domain
> It was there all the time.
>
>


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

  parent reply	other threads:[~2015-07-20 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 14:07 Jarek
2015-07-19 22:50 ` Andrey Repin
2015-07-20 17:52   ` Matt Seitz (matseitz)
2015-07-20 18:51     ` Jarek
2015-07-20 18:59   ` Jarek [this message]
2015-07-21  0:35     ` Andrey Repin
2015-07-21 14:30       ` Jarek
2015-07-21 20:50         ` Andrey Repin
2015-07-22 18:57           ` Jarek
2015-07-22 21:50             ` Andrey Repin
2015-07-24 19:05               ` Jarek
2015-08-02 12:47               ` Jarek

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=BLU436-SMTP217DCBDBFA0EED5BC1ACFFB9E850@phx.gbl \
    --to=yaro_29@hotmail.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).