Hi, I'm writing code to manage NTFS permissions. I looked at Win32::Perms, and may use that, but also found an application, setacl, that offers functionality through an ActiveX control (OCX), which can be used from any COM-enabled language. The author includes a sample perl script with the download, from which I've excerpted code below. Are there any advantages to using that vs. Win32::Perms? I contacted the author, and he's not really developing it anymore, and my gut feeling is that it isn't as well tested as Win32::Perms. But I wanted to post this question, since there may be issues that I'm not aware of. (I'm more a unix person, so I don't know all too well how perl works as 'COM-Enabled' language, among other things).

use strict;

use Win32::OLE qw(in with EVENTS);
use Win32::OLE::Const;


#
#	Start of script
#

# 	Create the SetACL object
my $oSetACL				=	Win32::OLE->CreateObject ('SetACL.SetACLCtrl.1') or die "SetACL.ocx is not registered on your system! Use regsvr32.exe to register the control.\n";

#	Load the constants from the type library
my $const				=	Win32::OLE::Const->Load ($oSetACL) or die "Constants could not be loaded from the SetACL type library!\n";

#	Enable event processing
Win32::OLE->WithEvents ($oSetACL, \&EventHandler);

#
#	Check arguments
#
my $Path					=	$ARGV[0] or die "Please specify the (file system) path to use as first parameter!\n";
my $Trustee				=	$ARGV[1] or die "Please specify the trustee (user/group) to use as second parameter!\n";
my $Permission			=	$ARGV[2] or die "Please specify the permission to set as third parameter!\n";
...

#	Set the object
my $RetCode				=	$oSetACL->SetObject ($Path, $const->{SE_FILE_OBJECT});