Mail Archives: cygwin/2006/06/20/19:41:44
Brian Hansen wrote:
> 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,
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?
<http://cygwin.com/faq/faq-nochunks.html#faq.api.secure>
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
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -