Re: Solving ntsec problems?

[Robert Collins <rbcollins at cygwin dot com>]

On Mon, 2002-11-04 at 15:35, Pierre A. Humblet wrote:
> At 09:09 AM 11/4/2002 +1100, Robert Collins wrote:
> >I'd rather extract the ntsec unix->win32 acl logic to a static library
> >that both cygwin1.dll and setup.exe can incorporate. 
> 
> Isolating ntsec in a library is a big job, unnecessary. 
> Setup probably needs only a small part of ntsec. Copying some 
> functions from sec_acl.cc and security.cc should be enough.

And will inevitable lead to skew in the future. Besides which, we don't
need *all* of ntsec in said library, only the stuff to be used by setup.
 
> It seems to me that the main thing we want setup to set is the acl 
> entry for the owner (which will Administrators if the user running
> setup is privileged) 

What if the user has setup their security differently? Say they want
'Security-Staff' as the grout for 'root' and 'Domain\\Administrator' as
the user for root?

Setting it wrongly in this environment would (AFAICT) cause problems.

Rob

-- 
---
GPG key available at: http://users.bigpond.net.au/robertc/keys.txt.
---

Attachment: signature.asc
Description: This is a digitally signed message part