This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: Non-trusted domain user causes mkpasswd and mkgroup to fail
- From: "Matt Seitz \(matseitz\)" <matseitz at cisco dot com>
- To: "Dave Korn" <dave dot korn at artimi dot com>, <cygwin at cygwin dot com>
- Date: Fri, 13 Jul 2007 11:35:51 -0700
- Subject: RE: Non-trusted domain user causes mkpasswd and mkgroup to fail
- Authentication-results: sj-dkim-3; header.From=matseitz@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
- References: <015b01c7c567$6f21fbf0$2e08a8c0@CAM.ARTIMI.COM>
From: Dave Korn [mailto:dave.korn@artimi.com]
>
> Let me repeat myself:
>
> >> If you aren't
> >> logged into the domain
> ^^^^^^^^^^^^^^^^^^^^^^
>
> Logging into the local machine and logging into the domain
> are two different
> things. When you are not logged in to the domain, it would
> be very very wrong
> for the domain controller to send you any information about
> the domain.[*]
Sorry, I guess I'm still not being clear. When I did "runas /netonly
/user:machine\user" followed by "mkpasswd -d machine -u user", I was
trying to create a "passwd" entry for a user account that was local to
the server named "machine". In other words, I was trying to access
information about the "machine\user" local user account. I was not
trying to access information about a domain user account.
Perhaps I'm confusing things by using the example name "user" in both
cases. Let me try restating it:
"runas /netonly /user:domain1\userA" followed by "mkpasswd -d domain1 -u
userA": works
"runas /netonly /user:machine2\userB" followed by "mkpasswd -d machine2
-u userB": fails
--
Matt Seitz
Manager, File System Virtualization
Cisco Systems, Inc.
.:|:.:|:.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/