X-Spam-Check-By: sourceware.org
Message-ID: <31b7d2790707212014n6c2d2904tea06199f31280b8b@mail.gmail.com>
Date: Sat, 21 Jul 2007 22:14:44 -0500
From: "DePriest, Jason R." <jrdepriest AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Non-trusted domain user causes mkpasswd and mkgroup to fail
In-Reply-To: <70952A932255A2489522275A628B97C304C8E845@xmb-sjc-233.amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <31b7d2790707131317r48a2b4ear1c917902f88aa68f AT mail DOT gmail DOT com> 	 <70952A932255A2489522275A628B97C304C8E845 AT xmb-sjc-233 DOT amer DOT cisco DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On 7/18/07, Matt Seitz (matseitz)  wrote:
> From: DePriest, Jason R.
> > On 7/13/07, Matt Seitz (matseitz)  wrote:
> > > "runas /netonly /user:machine2\userB" followed by "mkpasswd -d
> > > machine2 -u userB":  fails
> > >
> >
> > If the server is stand alone, wouldn't mkpasswd -l be more
> > appropriate than mkpasswd -d?
>
> That requires that I am able to run "mkpasswd" on the stand-alone
> server.  Unfortunately, I don't have that option in this case.  If
> "mkpasswd -l" allowed me to specify the name of another machine
> (something like "mkpasswd -l <machine> -u <user>"), then that might be a
> solution.
>
> --
> Matt Seitz
> Manager, File System Virtualization
> Cisco Systems, Inc.
> .:|:.:|:.
>

I have a complicated and untested idea that may or may not work, but
it is worth a shot since you aren't able to put Cygwin on the
stand-alone server to get a passwd file entry.

Try using a tool like psgetsid from Sysinternal's to get the SIDs of
the users you want to access your Cygwin system, then manually build
your own entries for your /etc/passwd file.

See http://cygwin.com/cygwin-ug-net/using-utils.html#mkpasswd and
http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-sids

-- 
NOTICE:  This email is being sent in clear-text across the public
Internet.  Therefore, any attempts to include unenforceable legalese
restrictions are ridiculous and pointless.  If you can read this,
consider yourself authorized (whether I like it or not).

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