|
File Transfer CS does not bypass security in anyway. It can not access any parts of your web server that can not already be accessed through a CGI program. If you are having trouble accessing specific resources using File Transfer CS , it is most likely a security problem that can only be resolved by working with your system administrator or Internet Service Provider (ISP) that manages your web server. Windows NT, Windows Internet Information Server (IIS) and Windows Internet Explorer (IE) interact in ways that go beyond basic web security. While these mechanisms provide more robust security, they can interfere with the execution of your application. And to resolve these problems requires an understanding of how these mechanisms interact. Security Topics |
|
User Authentication involves identifying and validating who the user is. Depending on how a user is authenticated, IIS will process the request under a specific NT account. IIS Authentication MethodsIIS supports three different methods of User Authentication:
The important thing to note about these three methods is what determines who the user is and how the user is logged on to NT. Establishing a Network LoginIf you need to access a network resource, such as a shared file system, from an ASP script, a network login must occur on the server. Furthermore, the login must occur under an account that has access permissions to the network resource. To ensure a network login, you have three options:
The first two options can be accomplished by using the IIS Console Manager to change the configuration of IIS. This may or may not be possible depending on whether or not you have administrative access to the server. To disable automatic password synchronization under IIS 4.0 follow these steps:
To disable NTLM Challenge/Response under IIS 4.0 follow these steps:
If neither of the first two options are possible, you may need to consider using the third option. Below is an example of how to log into the network using File Transfer CS :
In the above example, anonymous access is provided since the account and password are hardwired into the ASP script. The same account will always be used regardless of the user of your application. This technique is useful if the anonymous account does not have permissions to access the network resource, or it is not possible to disable IIS 4.0 automatic password synchronization.
If you want to authenticate each user, you will need to create an HTML form to collect login credentials that can then be passed to Computer.Impersonate. And while this technique suffers from the same security issues as Basic Authentication, it is no less secure, and can be used even if NTLM Challenge/Response is enabled.
|
Modifying NTFS Permissions from your scripts File Transfer CS provides interfaces for modifying NTFS permissions through the ACEs collection of File and Directory objects. To use File Transfer CS to modify an NTFS permission, the user account that your script is running under must own the file or that user account must have permission to Change Permissions. If the file or directory you are trying to access was created by your script, it is most likely that the user account that your script is running under does own the file.
|
|
User privileges are controlled by User Manager for Domains:
This shows both groups and users defined on your NT computer or domain. To change the rights for a user Choose Policies->User Rights. Rights required to modify the registryThe File.RegisterDLL method cannot be used if the process does not have write access to the system registry. In order to grant this right, follow the same procedure as above.
|