From: Corinna Vinschen <cygwin@cygwin.com>
To: Cygwin <cygwin@cygwin.com>
Subject: Re: sshd/cron seteuid() problem in latest CVS
Date: Mon, 15 Apr 2002 04:24:00 -0000 [thread overview]
Message-ID: <20020415131809.J29277@cygbert.vinschen.de> (raw)
In-Reply-To: <20020412152132.GC948@tishler.net>
On Fri, Apr 12, 2002 at 11:21:32AM -0400, Jason Tishler wrote:
> Using the latest CVS, I am getting the following Event Log error messages:
>
> o fatal: setuid 19695: Operation not permitted
> o (CRON) error (can't switch user context)
>
> with sshd and cron, respectively. After some debugging, I determined
> that the following patch is causing the problem:
>
> http://cygwin.com/ml/cygwin-cvs/2002-q1/msg00218.html
>
> The above patch needs to be reverted or reworked. See attached for an
> strace snippet.
>
> Note that I'm operating in a domain environment. My WAG is that this
> problem may not be apparent in a workgroup environment.
This isn't clear to me. The patch only changes the way, the PDC
is elicited. I don't see any connection especially with the below
strace snippet.
Corinna
>
> Thanks,
> Jason
> 1602 25198850 [main] sshd 836 seteuid: myself->gid: 513, gr: 268637752
> 2300 25201150 [main] sshd 836 set_process_privilege: 0 = set_process_privilege (SeCreateTokenPrivilege, 1)
> 5127879 30329029 [main] sshd 836 get_user_groups: 123 = NetUserGetGroups ()
> 979 30330008 [main] sshd 836 set_process_privilege: 1 = set_process_privilege (SeCreateTokenPrivilege, 0)
> 522 30330530 [main] sshd 836 create_token: -1 = create_token ()
> 206 30330736 [main] sshd 836 seteuid: create token failed, try subauthentication.
> 1212 30331948 [main] sshd 836 set_process_privilege: 0 = set_process_privilege (SeTcbPrivilege, 1)
> 60911 30392859 [main] sshd 836 extract_nt_dom_user: pw_gecos = 1003198A (U-TISHLERJASON\Administrator,S-1-5-21-1571110079-60108220-2047483585-500)
> 4446 30397305 [main] sshd 836 subauth: LsaLogonUser: -1073741702
> 1663 30398968 [main] sshd 836 set_process_privilege: 0 = set_process_privilege (SeTcbPrivilege, 0)
> 1127 30400095 [main] sshd 836 internal_getlogin: GetUserName() = SYSTEM
> 1271 30401366 [main] sshd 836 internal_getlogin: Domain: (null), Logon Server: \\PALO-ALTO-PDC, Windows Username: SYSTEM
> 225771 30627137 [main] sshd 836 internal_getlogin: Cygwins Username: SYSTEM
> 177 30627314 [main] sshd 836 seteuid: Diffs!!! token: -1, cur: 18, new: 500, orig: 18
> 439 30627753 [main] sshd 836 setuid: real: 18, effective: 18
>
> --
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting: http://cygwin.com/bugs.html
> Documentation: http://cygwin.com/docs.html
> FAQ: http://cygwin.com/faq/
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-04-15 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 8:23 Jason Tishler
2002-04-15 4:24 ` Corinna Vinschen [this message]
2002-04-17 8:25 ` Jason Tishler
2002-04-18 1:55 ` Corinna Vinschen
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=20020415131809.J29277@cygbert.vinschen.de \
--to=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).