Controversial what if.... we disable ntsec by default again?

Larry Hall cygwin-lh@cygwin.com
Tue Aug 5 15:55:00 GMT 2003


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
> default again?
>>> 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
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/


More information about the Cygwin mailing list

AltStyle によって変換されたページ (->オリジナル) /