X-Spam-Check-By: sourceware.org Message-ID: X-Sender: himhead@hotmail.com From: "Brian Hansen" To: cygwin@cygwin.com Subject: Security Vulnerabilities Date: Tue, 20 Jun 2006 16:44:01 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Hi, 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, Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/