Version 2.5.0
[Table of Contents]
WN Documentation Search Results -- Matches
You may select a new search term and repeat your search:
Matches
Here are the matching lines in their respective document sections.
Select one of the highlighted words in the matching lines below to jump
to that point in the document.
- Title: User's Guide for the WN Server
Matching lines:
- Conditional Text and Access Control
- Chapter 10: Limiting Access to Your WN
- Access Control Files: Limiting Access by
- Limiting Access by Password
- Access Control
- Granting Access to Your Home
- Title: An Overview of the WN server
Matching lines:
- server-side includes, access restrictions, etc. Some servers try to
- access to a file. A file can only be served if explicit permission to do
- the server is accessed via a
- Title: Installation and Setup of WN
Matching lines:
- also have to enter the names of the access and error
- reports since I do not have access to most of the UNIX variations. If
- and have minimal access permissions. In this situation the user
- nobody should not have ownership or write access of the
- with no special access privileges. If you are using an
- accessible to remote users on the Internet can be assumed perfectly
- /var/log/wnsd/access_log {
- Title: Creating your WN data directory
Matching lines:
- permissions possible. It needs to have read access to the files to be
- Likewise the index.cache file which controls access to
- Accessfile=/dir/access
- The Accessfile=
- line specifies the name of the file which controls access (by IP address)
- may be served to anyone. For more information on using the access
- mechanism see the chapter "Limiting Access to Your
- accessfile or a
- Access-denied-URL=http://host/dir/noaccess.html
- access control file is requested from an
- Access-denied-URL=noaccess.html
- Title: Security on the WN Server
Matching lines:
- The maintainer's objective is to prevent any unauthorized access to (or
- untrusted person has write access to any part of the WN
- database there granting illicit access to some documents on the server
- them to grant access to files owned by the same user as the
- access or is outside the server data hierarchy.
- system utility to further restrict the files which the server can access.
- internally accessing any file which is not in your data directory. If
- If it is possible make sure that no untrusted user has write access to
- with write access to your hierarchy can create an
- index.cache file which will give access to anything on your
- Note: Always assume that everyone with write access to any part
- Sometimes it is not possible or desirable to deny write access to your
- way to use access files or
- gaining access to files you are serving. They can simply make a symbolic
- server has access to the restricted file it will serve it if it is listed
- password or .access files) and
- WN offers two methods of limiting access to your hierarchy or
- parts of it. See the chapter "Limiting Access to
- access control files.
- The other method of limiting access is by password with the
- Maximum number of matches per file exceeded.
- Title: Setting Up Searches on the WN Server
Matching lines:
- directories have restricted access, only
- those directories which have the same access file or the same
- Accessfile=" directive
- necessarily be of the form "Accessfile=~/dir/.access" or
- "Accessfile=/dir/.access" rather than
- "Accessfile=.access").
- Title: Parsed Text and Server Side Includes on the WN server
Matching lines:
- accessing this document via any link which is not on the host
- 6.4 Conditional Text and Access Control
- access control file. For example:
- <!-- #if accessfile="secret/access" -->
- Hosts not listed in the file "secret/access" can't look at it, so why
- permitted by the access control file
- "secret/access".
- <!-- #if hostname =~ "\.uk$" && accessfile="secret/access" -->
- Something for those sites in accessfile but not in the UK.
- Title: Limiting Access to Your WN Hierarchy
Matching lines:
- Limiting Access to Your WN Hierarchy
- Limiting Access to Your WN Hierarchy
- There are two ways to limit access to your hierarchy. You can restrict
- access by hostname or IP address and you can restrict access to users
- (authentication). You can, of course, do both. To restrict access to an
- entire hierarchy you must restrict access to each of its subdirectories.
- Warning: If access to a directory is restricted by either of the
- 10.1 Access Control Files: Limiting Access by Hostname or
- If you have opted to limit access to your server in this way you do so by
- Accessfile= in the
- Accessfile=~/dir/.access
- specifies that the the access control file
- wnroot/dir/.access contains restrictions on what sites are
- allowed to access this directory. The
- Accessfile= directive
- directive occurs. In particular the access file must be located within
- directive is used in a directory with restricted access be sure the
- access file is not serveable. You can do this by giving it a name
- Also note that limiting access to this directory does not limit access to
- Accessfile= line must
- Maximum number of matches per file exceeded.
- Title: Users' Hierarchies and Personal Home Pages on the WN server
Matching lines:
- addresses by which the server is accessed.
- "/home/john/public_html" so the file accessed is
- has a data root that is accessed as "~jim" on
- Title: Multi-homed or Virtual Servers on the WN server
Matching lines:
- the hostname and port it is trying to access) the WN server will
- the IP address by which the server is accessed does not match any of the
- Title: WN Utility Programs
Matching lines:
- "Subject:"). Each link when accessed will produce a plain
- Title: WN Auxiliary Modules
Matching lines:
- authorization (authentication) or indexed searches or database access.
- You may wish the cache module function to have access to more information
- function to have access to more information about the request. If you
- access is granted, denied, or that an error occurred. Anyone writing an
- Title: Clickable Images and Imagemap files on the WN Server
Matching lines:
- causing the client to automatically access this URL.
- Title: Configuration File for the WN Package
Matching lines:
- /* #define WN_IP_ONLY_ACCESS */
- * Uncomment this if you will only use IP addresses in access control
- * name might be used for access control except when WN_IP_ONLY_ACCESS
- /* #define ACCESS_DENIED_URL "/noaccess.html" */
- /* #define NO_SUCH_FILE_URL "/noaccess.html" */
- * "Error 404 - Access denied, or file does not exist" condition
- Title: Format of index.cache file for WN
Matching lines:
- Title: Command Line Options for the WN Server
Matching lines:
- is in a directory with limited access or is
- Title: Command Line Options for WN Server wndex Utility
Matching lines:
- permitting access to all files in a directory without first creating
- option to grant access to a directory hierarchy without the need to
- Title: Index File Directives for the WN Server
Matching lines:
- Accessfile -- Specify directory
- access control file.
- Accessfile=/dir/accessfile
- specifies that the file /dir/accessfile is to be used to
- determine access privileges (by hostname or IP address) for this
- directory. If this line is omitted access is allowed for everyone.
- Both the path /dir/accessfile and the path
- ~/dir/accessfile are taken relative to the WN
- root directory. In particular the accessfile must be in the
- chapter "Limiting Access to Your WN
- Access-denied-URL --
- Set URL for requests for which access is denied.
- Access-denied-URL=http://host/dir/foo.html
- Access-denied-URL=/dir/foo.html
- Accessfile=" restriction should be
- #define ACCESS_DENIED_URL"
- foo.html does not have restricted access or you can
- Accessfile=" controlling the
- directory. A line in the accessfile will override any value set in
- Accessfile=" or a
- Maximum number of matches per file exceeded.
- Title: Parsed Document Syntax for the WN Server
Matching lines:
- #if accessfile" syntax
- #if accessfile" syntax
- contains the URL of the document containing the link accessed to
- C.1.2 Access Control Files
- The normal access control files used by
- WN to limit access to a directory can also be used to
- conditionally permit or deny access to text segments.
- #if accessfile="filename"
- -- Check access control file
- <!-- #if accessfile="/dir/accessfile" -->
- specifies that the file /dir/accessfile is to be used to
- determine access privileges (by hostname or IP address) for this text
- segment. The path /dir/accessfile is relative to the
- Limiting Access to Your WN Hierarchy"
- Title: CGI and other Environment Variables for the WN Server
Matching lines:
- Contains the type of authentication being used to limit access to
- Contains the name of the "virtual host" currently being accessed, if
- Title: Creating User Home Pages for the WN Server
Matching lines:
- access files and directories which are not heavily protected. Just to
- make sure the server won't have trouble accessing your home page run the
- E.2 Granting Access to Your Home Page
- So once your home page is functional, how do you access it? Well, your
- Title: Configuration Macros for WN
Matching lines:
- Title: Changelog for WN
Matching lines:
- documents with access control. Simplified code for log_logfile
- Fixed bug in wn/chkcntrl.c (syntax error when WN_IP_ONLY_ACCESS
- Fixed bug which made raw documents accessible when handled by
- Fixed bug which made source of scripts accessible. This is
- Access files now allow comments (starting with '#') to begin
- Fixed bug which made raw documents accessible when handled
- Fixed bug which made source of scripts accessible. This is
- NOACCESS and redirects correctly.
- Keyword/Title searches into access restricted subdirectories now
- work better. Instead of simply denying access, the restrictions
- when access should not be allowed.
- Added support for a group file to authwn. See docs/access.html.
- Access-denied-URL=http://host/dir/foo.html
- because of an accessfile restriction. The second it a URL to which
- Added support for a new additional format in access files restricting
- directory access to certain hosts. The new format for a line in an
- access file is
- will match (and allow access to) precisely those machines with IP
- run. For more details see docs/access.html.
- Added support for "privileged sites" in access files. If you list
- Maximum number of matches per file exceeded.
- Title: GNU Public License
Matching lines:
- access to copy from a designated place, then offering equivalent
- access to copy the source code from the same place counts as
- Title: GNU Free Documentation License
Matching lines:
- a publicly-accessible computer-network location containing a complete
- general network-using public has access to download anonymously at no
- Transparent copy will remain thus accessible at the stated location
- public access to a Transparent copy of the Document, and likewise
WN version 2.5.0
Copyright © 1998-2005 John Franks
<john@math.northwestern.edu>
licensed under the GNU Free Documentation License
Last modified: Sat June 18 2005
[Table of Contents]