How to prohibit the FSO on the server?

Three ways to disable FileSystemObject components
2002-6-4 Network pioneer

As we all know, the FileSystemObject component's powerful and destructive is its repeated free homepage
The reason for the disabling of providers (those that support ASP), which I sorted out, would have only found two ways, and later
Be stimulated by someone, just think of a third kind of unknown method, hehe, also do not know is this.

First: Use regsrv32/u C:\WINDOWS\SYSTEM\scrrun.dll (win98 path) to unregister the group
Thing This method is too vicious, belong to the method of destruction, we all have no use, is the next recruit

Second: Modify the value of the ProgID, the way in which the component is invoked in ASP is usually the Set object name =server.
CreateObject ("Progid"), this time we can modify the registry Progid value from the
To the method that disables the component. In the start-run regedit, and then find Hkey_classes_roo
T\scripting.filesystemobject, this time we can change the value of the ProgID, such as change
Into Scripting.filesystemobject8. This is called in the ASP page:
<%@ language=vbscript%>
<%
Set fs=server.createobject ("Scripting.filesystemobject8")
%>
(If you have not called the component before, you do not need to reboot, you can see the effect, otherwise please heavy
Look at the effect after Kai. )
This time we look at the result of the original invocation method:
<%@ language=vbscript%>
<%
Set fs=server.createobject ("Scripting.FileSystemObject")
%>
The results of this operation are:
Server object error ' ASP 0177:800401f3 '

Server.CreateObject failure

/aspimage/testfile2.asp, Line 3

800401f3
(OK, meet our requirements)
This method because I was late two steps, the result let others rob answer, so greatly stimulated me, knot
The result is a third method.

The third: Careful experts will think that, since you can modify the ProgID value to disable the component, the CLSID is
Is it possible to modify it? (OK, you want to be like me) we know that apart from the CreateObject method to
, you can also use the general <object> annotation to build a component, we can use the HTM in ASP
L <object> Callout To add a component to the Web page. The method is:
<object runat=server id=fs1 scope=page progid= "Scripting.filesystemobj
ECT "></object>
Runat representation is performed on the server side, scope represents the lifecycle of the component, and can be selected with SESSION,APPL
Ication or page (either the current page or the default)
This kind of writing is useless to us, there is another way of writing:
<object runat=server id=fs1 scope=page classid= "Clsid:clsid value" ></obj
Ect>
We can also disable the component by modifying the value of the CLSID, such as Hkey_classes_ro in the registry
The value of the Ot\scripting.filesystemobject\clsid 0d43fe01-f093-11cf-8940-00a0c90
54228 changed into 0d43fe01-f093-11cf-8940-00a0c9054229 (the last one), at this time of
Written as:
<object runat=server id=fs1 scope=page classid= "clsid:0d43fe01-f093-11
cf-8940-00a0c9054229 "></object>
See the results of the operation, no problem, OK. This time we'll use
<object runat=server id=fs1 scope=page classid= "clsid:0d43fe01-f093-11
cf-8940-00a0c9054228 "></object>
It's a mistake.

Create a new User: Iusr_domain
Set up anonymous users for the corresponding site in IIS Iusr_domain
CACLS: Setting Directory Permissions

This FSO is available, but will not affect others