auth_krb5 man page on YellowDog

Man page or keyword search:  
man Server   18644 pages
apropos Keyword Search (all sections)
Output format
YellowDog logo
[printable version]

AUTH_KRB5(8)		  InterNetNews Documentation		  AUTH_KRB5(8)

NAME
       auth_krb5 - nnrpd Kerberos v5 authenticator

SYNOPSIS
       auth_krb5 [-i instance]

DESCRIPTION
       This program does authentication for nnrpd against a Kerberos v5 KDC.
       This is NOT real Kerberos authentication using service tickets;
       instead, a username and password is used to attempt to obtain a Ker‐
       beros v5 TGT to confirm that they are valid.  As such, this authentica‐
       tor assumes that nnrpd has been given the user's username and password,
       and therefore is not as secure as real Kerberos authentication.	It
       generally should only be used with NNTP over SSL to protect the pass‐
       word from sniffing.

OPTIONS
       -i instance
	   If this option is given, instance will be used as the instance of
	   the principal received from nnrpd and authentication will be done
	   against that principal instead of the base principal.  In other
	   words, a principal like "user", when passed to auth_krb5 invoked
	   with "-i nntp", will be transformed into "user/nntp" before
	   attempting Kerberos authentication.

	   Since giving one's password to nnrpd is not as secure as normal
	   Kerberos authentication, this option supports a configuration where
	   all users are given a separate instance just for news authentica‐
	   tion with its own password, so their regular account password isn't
	   exposed via NNTP.

EXAMPLE
       The following readers.conf(5) fragment tells nnrpd to authenticate
       users by attempting to obtain Kerberos v5 TGTs for them, appending an
       instance of "nntp" to usernames before doing so:

	   auth kerberos {
	       auth: "auth_krb5 -i nntp"
	   }

	   access kerberos {
	       users: "*/nntp"
	       newsgroups: example.*
	   }

       Access is granted to the example.* groups for all users who success‐
       fully authenticate.

BUGS
       Currently, any username containing realm information (containing "@")
       is rejected.  This is to prevent someone from passing in a username
       corresponding to a principal in another realm that they have access to
       and gaining access to the news server via it.  However, this is also
       something that people may wish to do under some circumstances, so there
       should be a better way of handling it (such as, perhaps, a list of
       acceptable realms or a -r flag specifying the realm in which to attempt
       authentication).

       It's not clear the right thing to do when the username passed in con‐
       tains a "/" and -i was also given.  Right now, auth_krb5 will create a
       malformed Kerberos principal with multiple instances and attempt to
       authenticate against it, which will fail but perhaps not with the best
       error message.

HISTORY
       Originally written by Christopher P. Lindsey.  This documentation was
       written by Russ Allbery <rra@stanford.edu> based on Christopher's orig‐
       inal README file.

       $Id: auth_krb5.8 5912 2002-12-03 05:31:11Z vinocur $

SEE ALSO
       nnrpd(8), readers.conf(5)

       The latest version of Christopher's original nnrpkrb5auth may be found
       on his web site at <http://www.mallorn.com/tools/>.

INN 2.4.0			  2002-12-02			  AUTH_KRB5(8)
[top]

List of man pages available for YellowDog

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net