This is the mail archive of the
mailing list for the Cygwin project.
Re: Controversial what if.... we disable ntsec by default again?
- From: Larry Hall <cygwin-lh at cygwin dot com>
- To: Max Bowsher <maxb at ukf dot net>
- Cc: cygwin at cygwin dot com
- Date: Tue, 05 Aug 2003 11:43:25 -0400
- Subject: Re: Controversial what if.... we disable ntsec by default again?
- References: <02f301c35b4a$8e792f40$017c883e@starfruit>
- Reply-to: cygwin at cygwin dot com
Max Bowsher wrote:
Having ntsec on by default has shown us that the imperfect mapping between
ACLs and file modes can cause a *lot* of problems. Essentially, for ntsec to
be useful, a fair amount of caring for permissions is required. New users
are often not prepared for this. Hence: what about making ntsc off by
If not, I guess the ntsec code needs to be spun off into a seperate library,
where setup can get at it too.
Maybe I'm mistaken but I thought that (or something similar) was always the
plan. It sounds like forward motion to me as opposed to the alternative.
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