public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dale Lobb <Dale.Lobb@bryanhealth.org>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Cygwin openssh AllowGroups
Date: Thu, 17 Aug 2023 21:11:18 +0000	[thread overview]
Message-ID: <PH0PR16MB4782893F3EA5CBEC4408F37DF51AA@PH0PR16MB4782.namprd16.prod.outlook.com> (raw)

  Is there a known issue in Cygwin's implementation of openssh in the AllowGroups clause of sshd_config?  I cannot get it to work.

  I have a domain member server where I want to limit ssh logins to just members of a few groups.  Without those limits, any domain user can log into the server.  The AllowGroups clause of sshd_config appears tailor made for this purpose.,  But it does not work with either local groups or domains groups specified.  The AllowUsers clause works as documented, but listing out all the possible users would be tedious at best.

  I've searched back through the Cygwin archives, and there was a fair amount of chatter about this very issue 15 years ago or more, but none of the posts mention a general solution, other than to create a /etc/passwd file and list the group as the user's primary group.  But we aren't using /etc/passwd and /etc/group in Cygwin any more.  And even if that is the solution, it just moves the maintenance of the list from sshd_config to the passwd file.

  Anyone know how to get openssh AllowGroups to work in a more generic way like it does on a  true Linux system?

  Or am I barking up the wrong tree and no one uses Cygwin's openssh anymore?  I saw a recent post to this mailing list where the questioner was told to install Microsoft's distribution of openssh.

Best Regards,

Dale



________________________________

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

             reply	other threads:[~2023-08-17 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 21:11 Dale Lobb [this message]
2023-08-18  8:49 ` Corinna Vinschen
2023-08-24 14:56   ` EXTERNAL SENDER: " Dale Lobb

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=PH0PR16MB4782893F3EA5CBEC4408F37DF51AA@PH0PR16MB4782.namprd16.prod.outlook.com \
    --to=dale.lobb@bryanhealth.org \
    --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).