CVS: tmda-cgi/htdocs auth.ht,1.4,1.5 auth.html,1.7,1.8
Gre7g Luterman <[email protected]>
| Newsgroups | gmane.mail.spam.tmda.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/tmda/tmda-cgi/htdocs In directory sc8-pr-cvs1:/tmp/cvs-serv30527 Modified Files: auth.ht auth.html Log Message: Re-ordered the authentication methods to try and push sysadmins in the right direction the first time. Index: auth.ht =================================================================== RCS file: /cvsroot/tmda/tmda-cgi/htdocs/auth.ht,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- auth.ht 4 May 2003 23:46:06 -0000 1.4 +++ auth.ht 1 Jun 2003 04:54:15 -0000 1.5 @@ -3,10 +3,37 @@ <h2>Password Authentication</h2> <p>tmda-cgi currently has three possible authentication mechanisms:</p> <ul> - <li><a href="#FileAuth">File authentication</a> - <li><a href="#ProgAuth">Program authentication</a> (checkpassword-style) <li><a href="#RemtAuth">Remote authentication</a> + <li><a href="#ProgAuth">Program authentication</a> (checkpassword-style) + <li><a href="#FileAuth">File authentication</a> +</ul> + +<h3><a name="RemtAuth"></a>Remote Authentication</h3> +<p>tmda-cgi supports authentication by a remote host, using some common +existing protocols:</p> +<ul> + <li>imap + <li>imaps (secure SSL imap) + <li>apop + <li>pop3 + <li>ldap (requires separately obtained python ldap library) </ul> +<p>The authentication mechanism is specified as an URI in the regular URI +format: <tt>protocol://host.domain.com[:port][/ldap_domain]</tt> where +"protocol" must be from the list above, and the rest should be +self-explanatory.</p> + +<h3><a name="ProgAuth"></a>Program Authentication</h3> + +<p>tmda-cgi supports authentication by a checkpassword-style program + (see <a href="http://cr.yp.to/checkpwd/interface.html">a description</a> of + this interface). Typically, this is <tt>checkpassword</tt> or + <tt>vchkpw</tt>.</p> +<p>When specifying this method of authentication, you may need to supply + additional parameters to your checkpassword program. By default, + <tt>configure</tt> will append <tt>/bin/true</tt> or + <tt>/usr/bin/true</tt>, but any program that eventually returns + "0" will do.</p> <h3><a name="FileAuth"></a>File authentication:</h3> @@ -131,30 +158,3 @@ <tt>?debug=1</tt> onto the end of your CGI URL. This will display some diagnostic information if the login fails instead of simply saying "Wrong password. Try again."</p> - -<h3><a name="ProgAuth"></a>Program Authentication</h3> - -<p>tmda-cgi supports authentication by a checkpassword-style program - (see <a href="http://cr.yp.to/checkpwd/interface.html">a description</a> of - this interface). Typically, this is <tt>checkpassword</tt> or - <tt>vchkpw</tt>.</p> -<p>When specifying this method of authentication, you may need to supply - additional parameters to your checkpassword program. By default, - <tt>configure</tt> will append <tt>/bin/true</tt> or - <tt>/usr/bin/true</tt>, but any program that eventually returns - "0" will do.</p> - -<h3><a name="RemtAuth"></a>Remote Authentication</h3> -<p>tmda-cgi supports authentication by a remote host, using some common -existing protocols:</p> -<ul> - <li>imap - <li>imaps (secure SSL imap) - <li>apop - <li>pop3 - <li>ldap (requires separately obtained python ldap library) -</ul> -<p>The authentication mechanism is specified as an URI in the regular URI -format: <tt>protocol://host.domain.com[:port][/ldap_domain]</tt> where -"protocol" must be from the list above, and the rest should be -self-explanatory.</p> Index: auth.html =================================================================== RCS file: /cvsroot/tmda/tmda-cgi/htdocs/auth.html,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- auth.html 4 May 2003 23:46:06 -0000 1.7 +++ auth.html 1 Jun 2003 04:54:16 -0000 1.8 @@ -2,7 +2,7 @@ <?xml-stylesheet href="display/styles.css" type="text/css"?> <html> <!-- THIS PAGE IS AUTOMATICALLY GENERATED. DO NOT EDIT. --> -<!-- Sun May 4 18:44:52 2003 --> +<!-- Sat May 31 23:53:26 2003 --> <!-- USING HT2HTML 2.1 --> <!-- SEE http://ht2html.sf.net --> <!-- User-specified headers: @@ -73,10 +73,37 @@ <td valign="top" class="body"><h2>Password Authentication</h2> <p>tmda-cgi currently has three possible authentication mechanisms:</p> <ul> - <li><a href="#FileAuth">File authentication</a> - <li><a href="#ProgAuth">Program authentication</a> (checkpassword-style) <li><a href="#RemtAuth">Remote authentication</a> + <li><a href="#ProgAuth">Program authentication</a> (checkpassword-style) + <li><a href="#FileAuth">File authentication</a> +</ul> + +<h3><a name="RemtAuth"></a>Remote Authentication</h3> +<p>tmda-cgi supports authentication by a remote host, using some common +existing protocols:</p> +<ul> + <li>imap + <li>imaps (secure SSL imap) + <li>apop + <li>pop3 + <li>ldap (requires separately obtained python ldap library) </ul> +<p>The authentication mechanism is specified as an URI in the regular URI +format: <tt>protocol://host.domain.com[:port][/ldap_domain]</tt> where +"protocol" must be from the list above, and the rest should be +self-explanatory.</p> + +<h3><a name="ProgAuth"></a>Program Authentication</h3> + +<p>tmda-cgi supports authentication by a checkpassword-style program + (see <a href="http://cr.yp.to/checkpwd/interface.html">a description</a> of + this interface). Typically, this is <tt>checkpassword</tt> or + <tt>vchkpw</tt>.</p> +<p>When specifying this method of authentication, you may need to supply + additional parameters to your checkpassword program. By default, + <tt>configure</tt> will append <tt>/bin/true</tt> or + <tt>/usr/bin/true</tt>, but any program that eventually returns + "0" will do.</p> <h3><a name="FileAuth"></a>File authentication:</h3> @@ -201,33 +228,6 @@ <tt>?debug=1</tt> onto the end of your CGI URL. This will display some diagnostic information if the login fails instead of simply saying "Wrong password. Try again."</p> - -<h3><a name="ProgAuth"></a>Program Authentication</h3> - -<p>tmda-cgi supports authentication by a checkpassword-style program - (see <a href="http://cr.yp.to/checkpwd/interface.html">a description</a> of - this interface). Typically, this is <tt>checkpassword</tt> or - <tt>vchkpw</tt>.</p> -<p>When specifying this method of authentication, you may need to supply - additional parameters to your checkpassword program. By default, - <tt>configure</tt> will append <tt>/bin/true</tt> or - <tt>/usr/bin/true</tt>, but any program that eventually returns - "0" will do.</p> - -<h3><a name="RemtAuth"></a>Remote Authentication</h3> -<p>tmda-cgi supports authentication by a remote host, using some common -existing protocols:</p> -<ul> - <li>imap - <li>imaps (secure SSL imap) - <li>apop - <li>pop3 - <li>ldap (requires separately obtained python ldap library) -</ul> -<p>The authentication mechanism is specified as an URI in the regular URI -format: <tt>protocol://host.domain.com[:port][/ldap_domain]</tt> where -"protocol" must be from the list above, and the rest should be -self-explanatory.</p> </td> <!-- end of body cell --> </tr><!-- end of sidebar/body row --> _______________________________________ tmda-cvs mailing list http://tmda.net/lists/listinfo/tmda-cvs