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 content-class: urn:content-classes:message Subject: RE: Getting Cygwin into a corporation.. MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 25 Apr 2002 09:58:42 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Michael F. March" , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g3ONxFm23655 > -----Original Message----- > From: Michael F. March [mailto:march AT indirect DOT com] > Sent: Thursday, April 25, 2002 4:02 AM > To: cygwin AT sources DOT redhat DOT com > Subject: Getting Cygwin into a corporation.. > > > In the company I work for they have outlawed all Unix > variants (Linux, Solaris, OSX) from certain networks. I > asked why Cygwin could not be installed and here is > some of the response I got back: > > > Cygwin, in itself, is typically a harmless application. > > However, once installed, it does allow a user to invalidate > > the NT Security architecture; a user can then install cygwin > > ports without the NT administrators consent (including, of > > course, the cygwin DHCP port). > > How should I respond to this? Cygwin does not make installing applications easier or harder. It adds no executable types, and no alterations are made to system security. Long and short: if you can install DHCP with cygwin on those machines, you can install DHCP WITHOUT cygwin. Rob -- 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/