This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: Getting Cygwin into a corporation..
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Michael F. March" <march at indirect dot com>,<cygwin at sources dot redhat dot com>
- Date: Thu, 25 Apr 2002 09:58:42 +1000
- Subject: RE: Getting Cygwin into a corporation..
> -----Original Message-----
> From: Michael F. March [mailto:march@indirect.com]
> Sent: Thursday, April 25, 2002 4:02 AM
> To: cygwin@sources.redhat.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/