Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <4.3.1.2.20010808104233.02368f58@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Wed, 08 Aug 2001 10:45:40 -0400 To: joshua DOT newton AT dfs DOT com, cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: Silly question about OpenSSH and Cygwin In-Reply-To: <88256AA2.00500311.00@us-sfo-hub01.dfs> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 10:31 AM 8/8/2001, joshua DOT newton AT dfs DOT com wrote: >Is Cygwin still inherently insecure on a multiuser system, or is this a FAQ >entry that hasn't been >revised in a while? If it's still correct, is there any way to lock it down Cygwin itself is insecure so anything built on it is inherently insecure, at the local level. At this point, there are no implemented options to address this issue. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 118 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- 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/