Three ways to disable FSO

As we all know, the powerful function and destructive of FileSystemObject components is its frequent homepage

The reasons for providers (those supporting ASP), I have sorted it, I originally found two ways, I was stimulated by someone, hard to think of the third kind of method, huh, huh, I don't know if it is. Such.

The first: uses REGSRV32 / U C: /WINDOWS/SYSTEM/SCRRUN.DLL (WIN98 path) to log out of this component. This method is too vicious, belonging to the same way, everyone is not available, it is

The second: Modify the value of Progid, the way the component is called in the ASP is usually the SET object name = Server.createObject ("progid"), and we can achieve the disabled by modifying the progid value in the registry. method. In the start - run in regedit, then find hkey_classes_root / scripting.filesystemObject, then we can change the value of this ProgID, such as change to scripting.filesystemObject8. This is called in the ASP page:

<% @ Language = VBScript%>

<%

SET FS = Server.createObject ("scripting.filesystemObject8)

%>

(If you don't call the component in front, you can see the effect without restarting, otherwise you will be

Enter the effect. )

At this time, let's look at the results of the original call method:

<% @ Language = VBScript%>

<%

SET FS = Server.createObject ("scripting.filesystemobject")

%>

At this time, the results are:

Server object error 'ASP 0177: 800401F3'

Server.createObject failed

/ASPIMAGE/TestFile2.asp, line 3

800401F3

(OK, achieve our requirements)

This method is due to the later steps, and the result will let others have acknowledge, so greatly stimulate me, knot

There is a third method.

The third type: the careful master will think that since the component can be disabled by modifying the progid value, can the CLSID can also be modified? (OK, you think about me) We know, in addition to the createObject method, you can use a general