Serv-u 6002 version of the security settings of the full introduction (4)

Serv-u| Security | Introduction Open the registry to test the appropriate permissions, otherwise serv-u is not able to start. Enter the regedt32 point "OK" to continue at the start-> Run.

Locate the [Hkey_local_machine\software\cat Soft] branch. Right click on the above, select permissions, then point to Advanced, cancel the inheritable permission to allow the parent to propagate to the object and all child objects, including those explicitly defined here, click "Apply" to continue, then delete all the accounts. Click the OK button again to continue. A dialog box pops up that says "You denied all users access to cat Soft." No one can access Cat Soft, and only the owner can change permissions. Do you want to continue? , click "Yes" to continue. Then click the Add button to increase our established SSERVU account to the permissions list of the subkey, and give Full Control permission. The registry has been set up here. However, you cannot restart Serv-u because the installation directory is not yet set up.

Set it up now, just keep your admin account and SSERVU account, and give all the permissions except Full Control. (See Figure 13)


Figure 13:serv-u installation directory permission settings

Now, restarting the Serv-u FTP Server service in the service will start up normally. Of course, not completely set up here, your FTP users because there is no permission or login, so also set the permissions of the directory.

Suppose you have a web directory, the path is d:\web. In this directory, in the "Security settings" in addition to administrators and IIS users are deleted, and then add the SSERVU account, remember that the system account also deleted. Why do you have to set this up? Because it is now started with the SSERVU account, rather than with system privileges, the access directory is no longer used with system but SSERVU, and system is useless, so even if the overflow does not get system permissions. In addition, the root directory of the disk on which the web directory resides also sets the browse and read permissions for the Sserv-u account, and confirms that only that folder is set in the advanced level. (See Figure 14)


Figure 14:web Permissions settings on the disk where the directory resides

At this point, the setting is all over. The Serv-u settings are now set up in conjunction with IIS because it is impossible for web users to access the Serv-u directory with IIS using a different account, and the Web directory does not give system permission, so the system account also cannot access the Web directory, that is, You cannot back up the shell to your web directory even if you have the right to backup with MSSQL. You can safely use the serv-u.