Message-Id: <200603031401.k23E1k9P017669@tigris.pounder.sol.net>
From: cygwin AT trodman DOT com (Tom Rodman)
Reply-to: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: going thru domain switch..does cygwin grok "SID history"?
In-reply-to: <20060303084719.GC31264@calimero.vinschen.de>
References: <200603021513 DOT k22FDeoK009816 AT tigris DOT pounder DOT sol DOT net> <20060302152705 DOT GM3184 AT calimero DOT vinschen DOT de> <200603030024 DOT k230Ow2b012557 AT tigris DOT pounder DOT sol DOT net> <20060303084719 DOT GC31264 AT calimero DOT vinschen DOT de>
Date: Fri, 03 Mar 2006 08:01:46 -0600
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Fri 3/3/06 9:47 +0100 Corinna wrote:
--snip
> > The SIDs on several hundred GB worth of files and dirs will almost all
> > be from the old domain. The old domain controller will be shutdown,
> > but there will be a SID history associated w/(almost) each domain user
> > account and group that was in the old domain. This SID history will be
> > saved on the domain controler in the new domain.
> > 
> > So, if you run 'ls -l' in one of these directories whose files have SIDs
> > from the old domain, I'm wondering if the SID history mechanism will
> > work, showing the matching user or group in the new domain?
> 
> I have no idea and no experience at all with that.  Whatever happens,
> there's nothing in Cygwin which knows anything about AD and its deep
> mysteries, so any problems due to the SID history must be either
> solved on a deeper level of the OS, or it must be solved by manual
> intervention.  That's what I was trying to say.

OK, thanks again Corinna.

If needed, I have a method to swap in the new SIDs using 
a non cygwin opensource tool called setacl; I would use this to
fix the SIDs on our cygwin bash and perl scripts.  

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