Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <027701c35cf6$d11943f0$897c883e@starfruit> From: "Max Bowsher" To: "Mark Priest" , References: <02f301c35b4a$8e792f40$017c883e AT starfruit> <01c601c35b59$1fbaf930$6902a8c0 AT markonius> Subject: Re: Controversial what if.... we disable ntsec by default again? Date: Thu, 7 Aug 2003 15:48:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Mark Priest wrote: > Max, > > What problems is ntsec causing? I am a relatively new user and I have not > had any problems with it. In fact it is allowing me to host a more secure > ssh server installation. I have been following the list for a couple of > months and I have not seen many problems relating to ntsec. Most of those > that I have seen regarding ntsec seem to stem from configuration errors by > users rather than from anything inherent in ntsec. It is hard to comment > on this without knowing what the specific issues are. [Finally replying - been busy recently] Essentially, ntsec requires an understanding of the interaction between Cygwin and NT ACLs that first time users will not necessarily have. If you have that understanding, and are willing to spend the time to get things working as you want them - great!. But for an average single-user machine, ntsec can be a hinderance. Max. -- 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/