Update of /cvsroot/mod-auth/mod_authn_dbi
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv9599
Modified Files:
INSTALL README AUTHORS TODO
Log Message:
polished the documentation a little
Index: INSTALL
===================================================================
RCS file: /cvsroot/mod-auth/mod_authn_dbi/INSTALL,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -d -r1.2 -r1.3
--- INSTALL 25 Oct 2003 04:14:38 -0000 1.2
+++ INSTALL 25 Feb 2004 21:48:06 -0000 1.3
@@ -1,229 +1,6 @@
-Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
-Foundation, Inc.
-
- This file is free documentation; the Free Software Foundation gives
-unlimited permission to copy, distribute and modify it.
-
-Basic Installation
-==================
-
- These are generic installation instructions.
-
- The `configure' shell script attempts to guess correct values for
-various system-dependent variables used during compilation. It uses
-those values to create a `Makefile' in each directory of the package.
-It may also create one or more `.h' files containing system-dependent
-definitions. Finally, it creates a shell script `config.status' that
-you can run in the future to recreate the current configuration, and a
-file `config.log' containing compiler output (useful mainly for
-debugging `configure').
-
- It can also use an optional file (typically called `config.cache'
-and enabled with `--cache-file=config.cache' or simply `-C') that saves
-the results of its tests to speed up reconfiguring. (Caching is
-disabled by default to prevent problems with accidental use of stale
-cache files.)
-
- If you need to do unusual things to compile the package, please try
-to figure out how `configure' could check whether to do them, and mail
-diffs or instructions to the address given in the `README' so they can
-be considered for the next release. If you are using the cache, and at
-some point `config.cache' contains results you don't want to keep, you
-may remove or edit it.
-
- The file `configure.ac' (or `configure.in') is used to create
-`configure' by a program called `autoconf'. You only need
-`configure.ac' if you want to change it or regenerate `configure' using
-a newer version of `autoconf'.
-
-The simplest way to compile this package is:
-
- 1. `cd' to the directory containing the package's source code and type
- `./configure' to configure the package for your system. If you're
- using `csh' on an old version of System V, you might need to type
- `sh ./configure' instead to prevent `csh' from trying to execute
- `configure' itself.
-
- Running `configure' takes awhile. While running, it prints some
- messages telling which features it is checking for.
-
- 2. Type `make' to compile the package.
-
- 3. Optionally, type `make check' to run any self-tests that come with
- the package.
-
- 4. Type `make install' to install the programs and any data files and
- documentation.
-
- 5. You can remove the program binaries and object files from the
- source code directory by typing `make clean'. To also remove the
- files that `configure' created (so you can compile the package for
- a different kind of computer), type `make distclean'. There is
- also a `make maintainer-clean' target, but that is intended mainly
- for the package's developers. If you use it, you may have to get
- all sorts of other programs in order to regenerate files that came
- with the distribution.
-
-Compilers and Options
-=====================
-
- Some systems require unusual options for compilation or linking that
-the `configure' script does not know about. Run `./configure --help'
-for details on some of the pertinent environment variables.
-
- You can give `configure' initial values for configuration parameters
-by setting variables in the command line or in the environment. Here
-is an example:
-
- ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
-
- *Note Defining Variables::, for more details.
-
-Compiling For Multiple Architectures
-====================================
-
- You can compile the package for more than one kind of computer at the
-same time, by placing the object files for each architecture in their
-own directory. To do this, you must use a version of `make' that
-supports the `VPATH' variable, such as GNU `make'. `cd' to the
-directory where you want the object files and executables to go and run
-the `configure' script. `configure' automatically checks for the
-source code in the directory that `configure' is in and in `..'.
-
- If you have to use a `make' that does not support the `VPATH'
-variable, you have to compile the package for one architecture at a
-time in the source code directory. After you have installed the
-package for one architecture, use `make distclean' before reconfiguring
-for another architecture.
-
-Installation Names
-==================
-
- By default, `make install' will install the package's files in
-`/usr/local/bin', `/usr/local/man', etc. You can specify an
-installation prefix other than `/usr/local' by giving `configure' the
-option `--prefix=PATH'.
-
- You can specify separate installation prefixes for
-architecture-specific files and architecture-independent files. If you
-give `configure' the option `--exec-prefix=PATH', the package will use
-PATH as the prefix for installing programs and libraries.
-Documentation and other data files will still use the regular prefix.
-
- In addition, if you use an unusual directory layout you can give
-options like `--bindir=PATH' to specify different values for particular
-kinds of files. Run `configure --help' for a list of the directories
-you can set and what kinds of files go in them.
- If the package supports it, you can cause programs to be installed
-with an extra prefix or suffix on their names by giving `configure' the
-option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-
-Optional Features
-=================
-
- Some packages pay attention to `--enable-FEATURE' options to
-`configure', where FEATURE indicates an optional part of the package.
-They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-is something like `gnu-as' or `x' (for the X Window System). The
-`README' should mention any `--enable-' and `--with-' options that the
-package recognizes.
-
- For packages that use the X Window System, `configure' can usually
-find the X include and library files automatically, but if it doesn't,
-you can use the `configure' options `--x-includes=DIR' and
-`--x-libraries=DIR' to specify their locations.
-
-Specifying the System Type
-==========================
-
- There may be some features `configure' cannot figure out
-automatically, but needs to determine by the type of machine the package
-will run on. Usually, assuming the package is built to be run on the
-_same_ architectures, `configure' can figure that out, but if it prints
-a message saying it cannot guess the machine type, give it the
-`--build=TYPE' option. TYPE can either be a short name for the system
-type, such as `sun4', or a canonical name which has the form:
-
- CPU-COMPANY-SYSTEM
-
-where SYSTEM can have one of these forms:
-
- OS KERNEL-OS
-
- See the file `config.sub' for the possible values of each field. If
-`config.sub' isn't included in this package, then this package doesn't
-need to know the machine type.
-
- If you are _building_ compiler tools for cross-compiling, you should
-use the `--target=TYPE' option to select the type of system they will
-produce code for.
-
- If you want to _use_ a cross compiler, that generates code for a
-platform different from the build platform, you should specify the
-"host" platform (i.e., that on which the generated programs will
-eventually be run) with `--host=TYPE'.
-
-Sharing Defaults
-================
-
- If you want to set default values for `configure' scripts to share,
-you can create a site shell script called `config.site' that gives
-default values for variables like `CC', `cache_file', and `prefix'.
-`configure' looks for `PREFIX/share/config.site' if it exists, then
-`PREFIX/etc/config.site' if it exists. Or, you can set the
-`CONFIG_SITE' environment variable to the location of the site script.
-A warning: not all `configure' scripts look for a site script.
-
-Defining Variables
-==================
-
- Variables not defined in a site shell script can be set in the
-environment passed to `configure'. However, some packages may run
-configure again during the build, and the customized values of these
-variables may be lost. In order to avoid this problem, you should set
-them in the `configure' command line, using `VAR=value'. For example:
-
- ./configure CC=/usr/local2/bin/gcc
-
-will cause the specified gcc to be used as the C compiler (unless it is
-overridden in the site shell script).
-
-`configure' Invocation
-======================
-
- `configure' recognizes the following options to control how it
-operates.
-
-`--help'
-`-h'
- Print a summary of the options to `configure', and exit.
-
-`--version'
-`-V'
- Print the version of Autoconf used to generate the `configure'
- script, and exit.
-
-`--cache-file=FILE'
- Enable the cache: use and save the results of the tests in FILE,
- traditionally `config.cache'. FILE defaults to `/dev/null' to
- disable caching.
-
-`--config-cache'
-`-C'
- Alias for `--cache-file=config.cache'.
-
-`--quiet'
-`--silent'
-`-q'
- Do not print messages saying which checks are being made. To
- suppress all normal output, redirect it to `/dev/null' (any error
- messages will still be shown).
-
-`--srcdir=DIR'
- Look for the package's source code in directory DIR. Usually
- `configure' can determine that directory automatically.
-
-`configure' also accepts some other, not widely useful, options. Run
-`configure --help' for more details.
+NOTE: The main documentation of mod_authn_dbi lives at
+ http://mod-auth.sourceforge.net/docs/mod_authn_dbi/
+ See README for a quick'n'dirty ascii-conversion in
+ case you don't have a browser handy!
Index: README
===================================================================
RCS file: /cvsroot/mod-auth/mod_authn_dbi/README,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- README 25 Oct 2003 21:58:54 -0000 1.3
+++ README 25 Feb 2004 21:48:06 -0000 1.4
@@ -1,512 +1,647 @@
+This Apache Module is part of the "2.1 Authentication Project".
+Homepage: http://mod-auth.sourceforge.net/
-What is mod_authn_dbi?
-======================
-
-Auth*Provider for Apache 2.1-dev/2.2 using libdbi as a backend.
-This should allow use of many different databases, including MySQL, PgSQL, and Oracle.
[...999 lines suppressed...]
- password value will be accepted with any password that
- the user supplies. default for this option is "disabled"
+AuthnDbiUsernameField Directive
+-------------------------------
+Description: The table field that contains the username
+Syntax: AuthnDbiUsernameField DbiConfigName field
+Default: Username
+Context: server config
+Status: External
+Module: mod_authn_dbi
-5.) support for disabled passwords
- any account with "!" or "*" as value
- will be interpreted as locked account.
- basically this just suppresses a warning and
- could be done with IsActive ...but whatever :-}
- (actually, i needed it for an existing installation
- i plan to use mod_authn_dbi with)
+The name of the column that mod_authn_dbi will interpret as username.
Index: AUTHORS
===================================================================
RCS file: /cvsroot/mod-auth/mod_authn_dbi/AUTHORS,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -d -r1.3 -r1.4
--- AUTHORS 8 Feb 2004 06:12:31 -0000 1.3
+++ AUTHORS 25 Feb 2004 21:48:06 -0000 1.4
@@ -1,8 +1,79 @@
+This Apache Module is part of the "2.1 Authentication Project".
+
+Homepage: http://mod-auth.sourceforge.net/
+
+
Core Coding:
- Paul Querna
- Axel Grossklaus
+ Paul Querna <ch...@fo...>
+ Axel Grossklaus <ho...@us...>
Various Bug Fixes:
Rob Emanuele
Brice Tebbs
+
+
+
+PGP-Keys:
+
+
+pub 1024D/20EBD970 2004-02-25 Axel Grossklaus <ho...@us...>
+sig 3 20EBD970 2004-02-25 Axel Grossklaus <ho...@us...>
+sig 3 CAAED99D 2004-02-25 Axel Grossklaus <ax...@no...>
+sig 3 F6CA1C7F 2004-02-25 Axel Grossklaus <ag...@pr...>
+sub 4096g/4645EA72 2004-02-25
+sig 20EBD970 2004-02-25 Axel Grossklaus <ho...@us...>
+
+-----BEGIN PGP PUBLIC KEY BLOCK-----
+Version: GnuPG v1.2.2 (GNU/Linux)
+
+mQGiBEA8/88RBAC2mRvsvaY/UhFvgI213jvrRbGp7gq5hN4IYsT8Vi9/E87Lu9bc
+4WHGE1T8eC3WMbvF+x5F6mJ8ygEcPu37QWB9UiBDRR6ZflRF+GAZZ7Lmnz9jg9/o
+wRSyUjPXliodFb+em+YizFIJNsLXgl8T6PzQT4AA529RmOjTbFzSiklNzwCg5ATv
+3rrhR8TYTxMmXaDqjDRzNkMD/1YYin/YjNYzuLQ6h/RfVhRXNvS9sfv/xCIvxQCt
+w3u+soKyUC9vZ08lge97LKsND8ZrZbmX7ZeR1YI3aG9HoTLZHZ0VZ+w3dqkYWVDc
+KW3CvFayYKnqZcRZrcSe6Pk6Up/kg+HvEpDZBo9u8JAbTjWU5/QZYqpa6uTgkGgr
+KbzKA/4gmAPZluLxMefBFfFrmF3416S9WruRoVy3vqCcW9Eatp2GICYlABTmOH6D
+B7WOZhW/m4tYgvxjPLin1Ks5F9+CA9PU84ptDulpxi8HsOkRP95Ed5Ao64pngu1l
+zLVycHdDhgLEIgrftpZ89Qm9+Dv+N+tBjEbP8RD1wd7PmySZo7QsQXhlbCBHcm9z
+c2tsYXVzIDxob254QHVzZXJzLnNvdXJjZWZvcmdlLm5ldD6IXAQTEQIAHAUCQDz/
+zwcLCQgHAwIBAxUCAwMWAgECHgECF4AACgkQpFZkeiDr2XDXtgCfVCwcfs09qbEd
+2gJqH06GTS3UYVgAn0L1Q4bYMGT7RwXW8eyMwelqEoM+iJwEEwECAAYFAkA9AYUA
+CgkQjFo+Xcqu2Z3kPwQAmm5KxYF0fTOlKPnAAIycZHCs0lJP5YucY8tmloUVpGU0
+8OdvVcC4avjt8l8YxTHhImWDOz/Ea7TB6v1NVuxsqifGD0JYsnH6wnxRBms4kPyf
+WPsSwOJc3AIfaK7SfJCWyxAKLyFy7GpWKgNGWPgyD9bzWX4GY0HspECDWFQZ/7WJ
+ARwEEwECAAYFAkA9AbEACgkQfrjVWvbKHH+vyAf/f0A6h90ZnvlnS6vokVXpYaAB
+OkL6z/+NnjYCil9rIRGw2dt46TYJ4KfyCWIOTbtleoNy8Rk0MMTfWm+R4ws+jJQr
+gKTJdbGA3rhDg7e+mHqMzMNNO1QiCgb3HKzxjyKOW36VEF9XUVsYKA5AYitubfUZ
+c0+QXX2NgEBzNe7KkDdIa26jh+HvDidhtRaXYj4VxXngoFHuxAnXuOLHbg2iBwY2
+7leV1o9oQXaSTZWCbWAkwkiWmy9Vk3xcqVoQjwaqgUv8+4hCAV4RtgFwV7ldagsK
+NRsakYIieg7xVDt4WUkXURfrz5u5zYgfHmDA6g99Dnzrf8a4Qq5wHuSDbih6fLkE
+DQRAPQC5EBAA98rZUDNP/KmvDZn757IK/OSb1e5eZAu0jXEpootD4kZCd8+InX1S
+93sX/LkFU4dRB4SXP48gaZmr8RrmfrZESCpaUnNrhr/43gdNjjyhHj8Toy41AF0Z
+37MdDsga3dCZ+o0Tk5+6fA5hAYLF0khveUcEcX4qNpzfUS11z4e/M2Oljd6Kjoel
+JImU4nTw/YKpfyauInQO01gtSRHmDfeuiJlh2eZqezsfPEZWsoDHqGogRyXXsMPS
+6boMhiTebcXzsr5JMYP5sozWaP9ywXnYs3xvs1J3+ZGhD4p3vRtK5baGecLVFUUi
+i8QSvhAGWE3OxILLnY/sPxow6RzRqyXGo5kYVYelTrgi2KNRHXRYjNgTQyXFHjVU
+rudv8UZ7Kpzl7fW7JL0NzAfo421kBXbeu/zvv6Dl2T2+aDuDLitw5ndbj/a+oPhi
+7leIRGOfarm7zAY0pBdEATHPLsRZVw8kiFdYdhyX6/ejT0k4LzegCgpcTXrZwSf+
+aAmZddV6t+GKqe3M579O4Iq1WG02CNWbeTa5BiZzMDnpIzpcOK7W9XT0I7I06GQ0
+IgEW5E+g1m8KcWcC0W4nPsoYJ0Yv0PZbAa4UM50FUKJe3SmbGDBiG3jbFM7aZ+R6
+ZJHx17Qe5pdaLND42oAkofNN10zOF1rcdq7SBgtAsSydP2zDZtetVP8AAwUQAOYI
+d1/q/P8lq415WVHJbhGPsoE6NIDHuwJUtI+c8vO5ddwIO5RYlKPyDzAcFnkpAfC6
+PLzC/0Z2GyLGhXLfpFW8lY37/9A1QUUNFpKII5Y7eKclyfdt06JRFRe+8+bzb5dt
+C75iWVwn6/aCyVYb3RsCKBWHMUgU4usSint/08JhRWi8XMLwkoW0C85Tn3FFLMkd
+ZyZDf5/2YKWBZvLkT3Pd9n+VbQ3g/QHuwxealALqdqzJmsappfaH7SbwrnbqqCMt
+AsWdTLLcRSBIuOrxK5d6awq8tUxJgVF0Q5t/rTFY6nMgFyZw4/FlGMEYpy3hsiJu
+WKZpbypobWgqTZkroZhrL/06WIPtekmpVRsTdfnU0p4RNZXdptnRlvrlFG9z+T4/
+0mi66vmpC8BIM9JPQaiZ9N3ZbGjH8cmJBzvn8hi+NA6Hg3x7S5Ms+dmBV0xpUN6G
+Y2dvAJX6WKm8R1+pavjQACaBuhGKe2y6JSpVDU0qiuxp+UGuyUkm1Q8KhRkTo9Sv
+mTHGleil/zO5hETjmEu/cjapmYTPlKPunRwx8U6F7POL+8nO1XNo41eofMb5LJ9R
+1lU4CIEwe75bAFNY/afZddnIC47cSNahMO9FxChLGAmKH+zRu+7BLdBnZRQu/+ZO
+olTFm2bDeDFn9Woq3bcCJWmm2pp2ugb5hk+LqaPFiEYEGBECAAYFAkA9ALkACgkQ
+pFZkeiDr2XAFqgCgp0z/jPZoOn/5vyffp8Bm3+tGvQwAniqh60qDi2oCkZG2fYKS
+uN1+7IN8
+=EiPx
+-----END PGP PUBLIC KEY BLOCK-----
+
+
+
Index: TODO
===================================================================
RCS file: /cvsroot/mod-auth/mod_authn_dbi/TODO,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- TODO 8 Feb 2004 22:41:12 -0000 1.6
+++ TODO 25 Feb 2004 21:48:06 -0000 1.7
@@ -35,6 +35,8 @@
- PPC?
- Support mod_dbi_pool [chip?]
+----- Released Versions:
+
0.9.0
- Include HTML/XML Documentation in Releases?
- Create Plain Text XSL Stuff
@@ -42,15 +44,14 @@
+ Remove extra files from CVS (autoconf/make stuff we don't need) [chip]
? Have external people look for security issues (Prep for 1.0)
- Create "security-issues" contact address (for whole auth project?)
- - Mangle usernames [axel]
- - More SQL Variables [axel]
+ - Mangle usernames [axel/deferred for now]
+ - More SQL Variables [axel/done]
- Send Announcements:
- SourceForge
- FreshMeat [chip]
- modules.apache.org [chip]
- Other?
------ Released Versions:
0.0.7 + Create automake/configure scripts [chip]
+ Merge in Changes from Axel Grossklaus [axel]
|