This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Windows Security Hole??

I work in a large corporation with an obsessive security staff. Cygwin
now "accepted" (unofficially) through the "grease gun" method. In WWII
one Nazi gunmaker was developing the world's first assault weapon.
was informed of the effort - deemed it a waste of resources and ordered
project cancelled. A procurement general recognized the need for the
and quietly "forgot" to cancel the program. A year or so later, the
was produced and distributed to German soldiers on the Eastern front.
day Hitler met briefly with some field commanders from the Eastern front
asked if they needed anything. "We need more of these new guns!"

....  What new guns? Was Hitler's reply ....

Defying Hitler was NOT a good career move for anyone! So what do you
happened to the general who "forgot" to cancel the weapon program?????


Oh but what a risk he took indeed.

I took a similar risk where I work. Living by the philosophy that I can
anything until threatened with termination in a face to face meeting
plate threats in corporate mass e-mails are delete key fodder), I went
and used Cygwin and Perl to build an incredibly powerful automated
deployment and automated encrypted B2B communications infrastructure.
alternative is expenditure in the hundreds of thousands of dollars for
party software, licenses, consultants etc, etc. By the time I was
management was faced with a cruel dilemma - live by their own rules and
spend money they never budgeted for projects they never fully grasped
understood, or accept the "unacceptable" - production processes running
non-proprietary "open source" software. OH THE HORROR!!!

The result - I WAS COMMENDED.

The point is Windows ITSELF is a SECURITY HOLE. You'd hardly do worse
running cygwin on it if you have any kind of security consciousness and
good practices and policies. Your problem is, you were probably caught
"too early" before you could do something truly valuable and impressive
with it that would be VERY expensive to replace.

Everything in life is a cost-benefit analysis. Sell a benefit, or impose
a cost, and you will succeed in your agenda more often than not.
Unfortunately, the bigger the organization, the more SIGNIFCANT the cost
or benefit has to be to succeed in successfully creating change. Running
emacs is probably not "significant" enough - unfortunately.

-----Original Message-----
From: [] On Behalf
Of Dennis Russo
Sent: Wednesday, July 16, 2003 8:54 PM
Subject: Windows Security Hole??

Greetings all-
   I work for a corporation that is completly incased with windows.  I
currently have Win2K installed on my pc along with cygwin.  My security
dept became aware of this and now has asked me to remove cygwin because
it represents a security breetch to the organization.  Does running
cygwin open any security 'holes' in a Win2K networked environment??  My
thinking in this matter is that any information that I send while in
cygwin would get 'encapsulated' and passed to Windows to determine what
to do with it.  Therefore, any security setting (GPOs, etc) are still
enforced.  I'm really only using it to run my perl scripts and have
access to emacs.

  Any help or insight into this matter would be greatly appreciated... 


Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!

Unsubscribe info:
Problem reports:

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]