This is the mail archive of the
mailing list for the Cygwin project.
Re: Security Vulnerabilities
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 20 Jun 2006 19:41:08 -0400
- Subject: Re: Security Vulnerabilities
- References: <BAY110-F18CE44581A1613058A3705AB870@phx.gbl>
- Reply-to: cygwin at cygwin dot com
Brian Hansen wrote:
I'm trying to use cygwin at work, but the network administrator can't
approve it unless I can verify that the source code contains no obvious
signs of malicious code, back doors, Trojans, etc. I am fully confident
that these kinds of things would not be found in an open-source project
(because it would be so obvious), but I'm not able to analyze the source
code myself. The advantages of using cygwin for me at work are huge,
but I'm stuck unless someone can point me in the right direction. Is
anyone aware of a good way for me to prove that cygwin is secure to my
network admin? Any help would be greatly appreciated. Thanks,
Prove? Who can prove anything is secure to anyone? Can you prove Windows
is secure to him? Can he to you?
Irrational statements aside, did you look at the FAQ?
That's as good as you're going to get, which should be more than adequate
for your needs.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html