ASP tip: Disable FileSystemObject components

Filesystemobject| Tips | disable

As we all know, the power and destructiveness of the FileSystemObject component is why it is frequently disabled by free home providers (those that support ASP).

First: Unregister the component with the regsrv32/u C:\WINDOWS\SYSTEM\scrrun.dll (win98 path).

Second: Modify the value of the Progid, the way in which the component is invoked in the ASP is usually the Set object name =server.createobject ("Progid"), at which point we can change the method of disabling the component by modifying the Progid value in the registry. In the start-run regedit, and then find hkey_classes_root\ Scripting.FileSystemObject, this time we can change the value of the rogid, such as change to 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 reboot to see the effect.) )
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 to meet our requirements.
Third: You can disable the component by modifying the ProgID value, which can also be done by modifying the CLSID.
We know that in addition to the CreateObject method, you can also use the general <object> annotation to create a component, we can use the HTML <object> annotation in the ASP, in order to add a component to the Web page. 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 chosen either by session,application or page (representing the current page, or by default) this is not working for us, there is another way:
<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_ in the registry Classes_root\scripting.filesystemobject\ The value of the CLSID 0d43fe01-f093-11cf-8940-00a0c9054228 changed to 0d43fe01-f093-11cf-8940-00a0c9054229 (after the last one), this time the wording is:
< 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 use <object runat=server id=fs1 scope=page classid= clsid:0d43fe01-f093-11cf-8940-00a0c9054228 "></" Object> made a mistake at this moment.

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