RE: Win32::Perms

[Kirk Batzer]

Title: Message

Dave,

 

It's a shame you no longer have the resources for supporting the Win32-Perms module. This is the only scripting module that I've seen that comes close to making sense of ACL permissions on Win32 Objects.  The NTFileSecurity module doesn't even come close. 

 

I even find the Win32-Perms complex and still don't understand all the complexities of Win 32 permissions. There are differences in what I see in the Explorer Security window and what is returned from the Win32-Perms scripts.  The answer requires a more complete knowledge of the Win32 objects and OS.  This is beyond the scope of most System Administrators and more for Win32 OS Developers.   

 

I wish there was more discussion and work on scripting Win32 Access permissions and ACL'S.  I've spend time searching the Microsoft News boards: msnews.microsoft,com and find little on scripting and access permissions. 

 

On UNIX Systems, setting and displaying access permissions is standard scripting for System Admins.  On Windows machines it's almost impossible.  

 

I find that Microsoft's WMI technology is not mature. I use it when I can, but I cross my fingers at the same time. Many sample WMI _vbscript_s will not run correctly on many of my Windows machines. WMI is much too ingrained in the OS, and will expectedly die if you have locked down your machine for security reasons.  Finding answers is near impossible too. 

 

I appreciate all the effort you and Roth Consulting group has done for the PERL community.  I also hope to see some type of wrapper on access and setting Win32 ACL'S in the future. 

 

 

 

Kirk W. Batzer

Enterprise Systems and Operations

 

Rutgers University
65 Davidson Rd.
Piscataway, NJ 08854
Phone:  (732) 445-6266
Fax:    (732) 445-5493
Email:  [EMAIL PROTECTED]

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Roth
Sent: Friday, March 11, 2005 2:35 AM
To: Chris Wagner; perl-win32-admin@listserv.ActiveState.com
Subject: RE: Win32::Perms

You are right that WMI is a good alternative to Win32::Perms (and since my team has no resources to work on this module it is a good idea to make use of WMI).

 

---

From: [EMAIL PROTECTED] on behalf of Chris Wagner
Sent: Thu 3/10/2005 9:35 AM
To: perl-win32-admin@listserv.ActiveState.com
Subject: Win32::Perms

Since I see that his Excellency Dave Roth reads this mailing list I'll throw
this out there for him or anybody who knows.  I'm using Win32::Perms with
great effect on a network audit.  However some of them are failing that
"shouldn't".  I use Lanman to get the share list on a host then use Perms to
get the permissions on each shared directory (not the share point).
Creating the perms object usually succeeds unless it's blocked by an Access
Denied.  unless ( $cperm = new Win32::Perms($unc) ) {.....}  $unc is like
\\123.0.0.1\bob\  The problem comes when I call Dump on it, $cperm->Dump(
[EMAIL PROTECTED] ).  Sometimes this will fail which means either there are no
permissions at all or we don't have permission to get the permissions.  Now
if I take one of these failures are go to the UNC in Windows Explorer, I
*can* see the permissions, with the same logon as the script, except that
explorer admonishes "You only have permission to view ...".  Then when I
drill into the permissions it shows that Everyone has the "Read Permissions"
flag.  So why does Win32::Perms die on this when Explorer works?  My guess
is that Perms is trying to open the object as read/write when we only have
"read".  Dave?

As an aside, is there another way to grab the permissions?  I'm thinking WMI
or OLE.







--
REMEMBER THE WORLD TRADE CENTER         ---=< WTC 911 >=--
"...ne cede males"

00000100

_______________________________________________
Perl-Win32-Admin mailing list
Perl-Win32-Admin@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs

_______________________________________________
Perl-Win32-Admin mailing list
Perl-Win32-Admin@listserv.ActiveState.com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs