From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1983 invoked by alias); 6 Dec 2002 14:35:44 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 1966 invoked from network); 6 Dec 2002 14:35:40 -0000 Received: from unknown (HELO rtp-msg-core-1.cisco.com) (161.44.11.97) by sources.redhat.com with SMTP; 6 Dec 2002 14:35:40 -0000 Received: from goblet.cisco.com (localhost [127.0.0.1]) by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id gB6EZvkT008360; Fri, 6 Dec 2002 09:35:58 -0500 (EST) Received: from brosler-ccna3.cisco.com (dhcp-161-44-175-135.cisco.com [161.44.175.135]) by goblet.cisco.com (Mirapoint) with ESMTP id ACF41656; Fri, 6 Dec 2002 09:35:27 -0500 (EST) Message-Id: <4.3.2.7.2.20021206092618.017d0130@goblet.cisco.com> X-Sender: brosler@goblet.cisco.com Date: Fri, 06 Dec 2002 06:36:00 -0000 To: Vince Hoffman From: "Bruce P. Osler" Subject: RE: Is it possible to use centralized passwords with cygwin inetd ? Cc: "'Bruce P. Osler'" , cygwin@cygwin.com In-Reply-To: <3500515B75D9D311948800508BA379559509C4@EX-LONDON> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-SW-Source: 2002-12/txt/msg00357.txt.bz2 I guess I was looking for something a bit more dynamic. I understand that I can create entries on my local machine which contain the domain users password. The issue for me is one of centralization. Is there a way I can bypass the local /etc/passwd file in order that cygwin directly queries the network resource. To do this I would imagine an exchange similar to the following would have to be seen: brosler@WHEREVER-NT ~ $ telnet brosler-nt Trying 172.27.57.214... Connected to brosler-nt.foobar.com. Escape character is '^]'. CYGWIN_NT-4.0 1.3.15(0.63/3/2) (brosler-nt) (tty0) login: FOOBAR_ENG\brosler password: brosler-nt@BROSLER-nt ~ $ In this instance the /etc/passwd file would NOT contain an entry for this specific user, but rather it would contain an entry for something like "U-FOOBAR_ENG\everyone" or some such thing which would cause the passwd agent to direct the query to the network instead of at the local passwd file. I mean, inside cisco there's something on the order of 40000 employees. In my imediate group there's over 400. The idea that all of them are never going to change their password is ludicrous as well as the nature of having to pull down 400 passwords on a periodic basis (NT reboots are not an unknown :-) As all this password stuff is already accounted for on a network server somewhere in the ether, why not take advantage of it. - Bruce At 10:41 AM 12/6/2002 +0000, Vince Hoffman wrote: >Cygwin fully supports domain users. just run `mkpasswd -d >> >/etc/passwd` on each box. >(setup may run this automaticly these days i'm not sure so check if you >already have a list of domain users in your passwd file.) > > > > -----Original Message----- > > From: Bruce P. Osler [mailto:brosler@cisco.com] > > Sent: 05 December 2002 22:04 > > To: cygwin@cygwin.com > > Cc: Bruce Osler > > Subject: Is it possible to use centralized passwords with > > cygwin inetd? > > > > > > For starters - I'd like to contribute to the Cygwin love-fest going > > on. I think Cygwin is an awesome environment with huge benefits > > for folks working under windows. > > > > Today I'm interested in finding out wether I can use networked > > password services with the cygwin inetd. At work I would like to > > setup a series of computers with Cygwin tools all of which are > > running the Cygwin inetd. As there are a couple of hundred engineers > > in this environment the option of maintaining multiple /etc/passwd > > files is a bit onerous (if not unreasonable). All of these computers > > are already hooked into an environment where the user passwords are > > provided and managed centrally to an NT domain. Is there any way > > I can have Cygwin/inetd use the central domain password service > > for authentication? > > > > - Bruce > > > > > > -- > > 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/ > > > >-- >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/ -- 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/