Well, sometimes just asking the question gets your mind working in new paths. I discovered that the Set method that I was using tries to set the SACL, owner and group as well as the DACL. Setting the Owner requires the Take Ownership privilege which is by default restricted to administrators. By using SetDacl instead, I was able to accomplish my DACL change without needed unusual privileges. DUH!
Tim MacAlpine (a tad more enlightened!) [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > -----Original Message----- > From: MacAlpine, Tim > Sent: Wednesday, March 27, 2002 8:32 AM > To: '[EMAIL PROTECTED]'; > '[EMAIL PROTECTED]'; > '[EMAIL PROTECTED]' > Subject: Perms question > > I found a reference to Win32::Perms in one of the activestate lists as an > alternative to Win32::FileSecurity. (My code using Win32::FileSecurity > stopped working when I moved it to Win2k from NT 4.0. There seems to be a > problem adding domain accounts to file ACLs - something about the name > lookup.) Anyway, I downloaded Win32::Perms, which looks to be a very > robust module. However, I can only seem to get it to successfully set an > ACL if I'm running as a local administrator - my normal user fails to set > ACLs and when I print out $^E I get "Not all privileges referenced are > assigned to the caller." I'm trying to find out what privilege it is that > Perms requires. > > Since I'm behind a proxy server I can't get direct access to the Roth > Perms newgroup. Has anyone on this list used this module with success > under Windows 2000? > > Thanks, > > Tim MacAlpine > [EMAIL PROTECTED] _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
