Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: Fwd: Re: cron and NT domains References: <20020723104728 DOT A13588 AT cygbert DOT vinschen DOT de> From: Don Dwiggins Date: 23 Jul 2002 08:43:09 -0700 In-Reply-To: <20020723104728.A13588@cygbert.vinschen.de> Message-ID: Lines: 23 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-OriginalArrivalTime: 23 Jul 2002 15:43:10.0031 (UTC) FILETIME=[A58935F0:01C2325F] Corinna Vinschen writes: > On Mon, Jul 22, 2002 at 07:23:30PM -0700, David MacMahon wrote: >> So are you saying that IF one is running Win 2K or XP AND using an >> active directory server AND the active directory server is configured to >> disallow anonymous access, THEN cygwin apps like cron and sshd are >> unable to switch user context to a domain user without a password? ... > I'm thinking about a small patch which would allow you to work with only > the user data given in /etc/passwd and /etc/group to change user context. FWIW, from my playing around with cron, it seems that it _does_ switch context to a domain user -- sort of. In particular, doing an "id" in the script started by cron showed me the domain user's uid and SYSTEM's gid; however, the script couldn't mount a network drive with "net use" unless the password was supplied. It seems as though you're a domain user, but with only access to the local machine. -- Don Dwiggins "The truth will make you free, d DOT l DOT dwiggins AT computer DOT org but first it will make you miserable" -- Tom DeMarco -- 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/