r11036 - /trunk/libapache-authenhook-perl/debian/control

[roberto at users.alioth.debian.org]

Author: roberto
Date: Sun Dec  9 04:59:56 2007
New Revision: 11036

URL: http://svn.debian.org/wsvn/?sc=1&rev=11036
Log:
Trim down long description

Modified:
    trunk/libapache-authenhook-perl/debian/control

Modified: trunk/libapache-authenhook-perl/debian/control
URL: http://svn.debian.org/wsvn/trunk/libapache-authenhook-perl/debian/control?rev=11036&op=diff
==============================================================================
--- trunk/libapache-authenhook-perl/debian/control (original)
+++ trunk/libapache-authenhook-perl/debian/control Sun Dec  9 04:59:56 2007
@@ -17,23 +17,3 @@
  API in Perl.  This is different than the authentication API
  from Apache 1.3 or even Apache 2.0, but in its differences lies
  strength.
- .
- For a full description of how authentication works in 2.1, see
- .
- http://www.serverwatch.com/tutorials/article.php/2202671
- .
- Basically, the difference between 2.0 and 2.1 is that authentication
- is now delegated to providers, and each provider has a specific
- purpose.  For instance, mod_authn_file covers gleaning the password
- from an .htpasswd or .htdigest file, while mod_auth_basic covers
- the Basic dialogue between the client and server, regardless 
- of the source of the password.  The best part of all this (to me)
- is that Digest authentication is also delegated out - 
- mod_auth_digest now handles all the intricacies of Digest
- authentication (including the elusive MSIE support) which
- means you don't need to worry about them (and neither do I).
- All that Digest authentication requires is *some* authentication
- provider to provide user credentials - this can be via
- mod_authn_file or another mechanism of your choosing.
- .
- This description was automagically extracted from the module by dh-make-perl.