From: Sam Habiel <sam.habiel@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Help with sgid into the Administrators group (or alternatives?)
Date: Fri, 08 Jun 2018 13:34:00 -0000 [thread overview]
Message-ID: <CABHT963fN-ATo=4gjop3rMtZ5U53=JX_t1BOyUnM0WQtB+87fA@mail.gmail.com> (raw)
In-Reply-To: <CABHT961S4_s8A=eBJNUKOU3vGMh_D_s_ACUqaFbswsgmMzq7cg@mail.gmail.com>
I installed the LSA authentication package; but no difference in
behavior was found.
--Sam
On Wed, Jun 6, 2018 at 9:20 AM, Sam Habiel <sam.habiel@gmail.com> wrote:
> I am continuing to port GT.M to Cygwin
> (https://www.fisglobal.com/solutions/banking-and-wealth/services/database-engine).
>
> The database has a suid program that is marked u+s (root suid) on the
> file permissions so that it can run as root whenever invoked. One of
> the first things it does is cd to another directory that is owned by
> root and is not accessible by anybody else.
>
> Cygwin doesn't have the concept of root; so I am trying to implement
> this by sgid into the Adminstrators group (544) from a limited user
> account (i.e., set-up that way on Windows). The executable, instead of
> being suid root, is sgid Adminstrators. The sgid C call apparently
> succeeds when I run it from gdb, but the C chdir instruction fails.
>
> I read https://cygwin.com/cygwin-ug-net/ntsec.html; but haven't done
> anything it says. After all, the sgid call apparently succeeded.
>
> My question is: am I on the right path; or is Windows and Cygwin being
> reasonable in denying my request to chdir when the user is not a
> member of the Administrators group, in spite of the executable being
> sgid Administrators?
>
> --Sam
--
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:[~2018-06-08 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 13:20 Sam Habiel
2018-06-08 13:34 ` Sam Habiel [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='CABHT963fN-ATo=4gjop3rMtZ5U53=JX_t1BOyUnM0WQtB+87fA@mail.gmail.com' \
--to=sam.habiel@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).