X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <49D5B276.5050701@gmail.com>
Date: Fri, 03 Apr 2009 07:53:42 +0100
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Promoting cygwin system to member server
References: <01N7AZJAP67S8XW3IJ AT ecr6 DOT ohio-state DOT edu>
In-Reply-To: <01N7AZJAP67S8XW3IJ@ecr6.ohio-state.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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

Michael T. Davis wrote:

> We have a standalone server running Windows Server 2003 SP2.  We would like
> to promote it to a member server in an existing Windows domain.  Will this 
> affect how cygwin accounts are managed and maintained?  We want to preserve
>  the functionality of the existing local accounts, and be able to continue
> to manage them (add, remove, etc.) so that the users can continue to use
> cygwin (esp. the SSH server) independent of the Windows domain.  (In fact,
> we don't want domain users to access the system via cygwin's SSH server,
> only local users.)

  I can't say for sure but advise caution.  I once installed Cygwin as a local
machine user on a non-domain machine which I then joined to a domain and found
some screwy perms settings, but I just fixed them and got on with what I was
doing rather than investigate, so I don't even know whether it was related.
That was on a simple install with no services set up; your arrangement is more
complex.  The best advice I can give in the circumstances is to use a system
imaging (or other backup) tool, try it, and test thoroughly.

> we don't want domain users to access the system via cygwin's SSH server,
> only local users.)

  That bit should be easy; just don't use the -d option when generating
/etc/{passwd,group} and don't add their keys to the sshd authorized keys file.

    cheers,
      DaveK



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