Hehe, yeah, this is a fun one.
First, there is a utility (vbscript) available to help you set permissions:
http://support.microsoft.com/kb/267904
Second, if you can avoid using anonymous access, that's best. Use
impersonation to tell your ASP code "act like the user that is using
this".
I just saw your "NO VBSCRIPT" comment... sorry about that.
I was looking at this exact problem about a month ago because I wanted
to stay away from scripts as well. P-Invoke is an ugly but
sometimes necessary approach when it comes to ACE/ACL. I know
Microsoft is adding new permission toys in 2.0.
This may be of help:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/setting_user_security.asp
"Note A NULL ACL in the
SECURITY_DESCRIPTOR grants unlimited access to everyone all the time. For more information about the implications of unlimited access, see
Creating a Security Descriptor for a New Object."
<still looking for a better answer... will revise this in a few.. I want to know as well

>