SitePoint Sponsor

User Tag List

Results 1 to 3 of 3
  1. #1
    SitePoint Wizard westmich's Avatar
    Join Date
    Mar 2000
    Location
    Muskegon, MI
    Posts
    2,328
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Does anyone know the difference between Read, Execute, and Scripts when enabling 'Web Sharing' on folders on the PWS? I guess Read would be low level access for the browser to simply read the files within an enabled directory. Furthermore, I would guess that Scripts means the server will process scripts within the files like ASP, PHP, or ColdFusion.

    So where does execute come in? Is it a greater security risk to have it enabled? Do I need for ASP?
    Westmich
    Smart Web Solutions for Smart Clients
    http://www.mindscapecreative.com

  2. #2
    Your Lord and Master, Foamy gold trophy Hierophant's Avatar
    Join Date
    Aug 1999
    Location
    Lancaster, Ca. USA
    Posts
    12,305
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    With Execute permissions, any .EXE or shortcut in that folder can be accessed. So if you place a copy of Explorer.exe or a shortcut to it in that directoy, you just opened your entire system up.
    Wayne Luke
    ------------


  3. #3
    SitePoint Wizard wdmny's Avatar
    Join Date
    Jul 2000
    Location
    Here
    Posts
    1,010
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    You should at most keep it at scripts unless you really, really need an executable, otherwise, just use scripts.

    I copied this from IIS directory security help so you can see MS's definitions, etc...

    -----------------------------------------------------------

    Script source access
    To allow users to access source code if either Read or Write permissions are set, select this option. Source code includes scripts in ASP applications. For more information, see Setting Web Server Permissions.

    Read
    To allow users to read or download files or directories and their associated properties, select this option.

    Write
    To allow users to upload files and their associated properties to the enabled directory on your server, or to change content in a Write-enabled file, select this option. Write can only be done with a browser that supports the PUT feature of the HTTP 1.1 protocol standard.

    Directory browsing
    To allow the user to see a hypertext listing of the files and subdirectories in this virtual directory, select this option. Virtual directories will not appear in directory listings; users must know a virtual directory’s alias.

    Important Your Web server will display an “Access Forbidden” error message in the user’s Web browser if the user attempts to access a file or directory and both of the following items are true:

    Directory browsing is disabled.
    The user does not specify a file name, such as Filename.htm.

    Log visits
    To record visits to this directory in a log file, select this option. Visits are recorded only if logging is enabled for this Web site. For more information, see Logging Site Activity.

    Index this resource
    To allow Microsoft Indexing Service to include this directory in a full-text index of your Web site, select this option.

    Application Settings
    An IIS Web-based application is defined by the directory structure in which it is located. For more information, see About Applications. To create an application, see Creating Applications.

    Execute Permissions
    This determines what level of program execution is allowed for this site or virtual directory resources. For more information, see Setting Web Permissions.

    None Only static files, such as HTML or image files, can be accessed.

    Scripts only Only scripts, such as ASP scripts, can be run.

    Scripts and Executables All file types can be accessed or executed.

    Application Protection
    Select whether applications are run in the same process as Web services (low), in an isolated pooled process in which other applications are also run (medium), or in an isolated process separate from other processes (high).

    A redirection to a URL
    These properties appear when you select A Redirection to a URL. Redirects a virtual directory to the destination URL without adding any other portions of the original URL. You can use this option to redirect an entire virtual directory to one file. For example, to redirect all requests for the /scripts virtual directory to the file Default.htm in the home directory, type /Default.htm in the Redirect To text box and select this option.

    A directory below this one
    Redirects a parent directory to a child directory. For example, to redirect your home directory (designated by /) to a subdirectory named /newhome, type /newhome in the Redirect To text box and select this option. Without this option, the Web server will continually map the parent to itself.

    A permanent redirection for this resource
    Sends the following message to the client: “301 Permanent Redirect.” Redirects are considered temporary, and the client browser receives the following message: “302 Temporary Redirect.” Some browsers can use the “301 Permanent Redirect” message as the signal to permanently change a URL, such as a bookmark.

    Redirect Variables
    Use redirect variables to pass portions of the original URL with the destination URL. For more information, see Redirect Reference.

    Redirect Wildcards
    Use redirect wildcards to match any number of characters in the original URL. For more information, see Redirect Reference


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •