oysteikt/heimdal
0
0
Fork 0
Code Issues 5 Pull Requests Releases Activity

texinfo-multiple-files-update

Browse Source 
git-svn-id: svn://svn.h5l.se/heimdal/trunk/heimdal@16772 ec53bebd-3082-4978-b11e-865c3cabbd6b
This commit is contained in:
Johan Danielsson
2006-02-27 13:00:51 +00:00
parent 2faf329cf4
commit 21f7a5f9ad
3 changed files with 86 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
doc/heimdal.texi
View File

@@ -178,14 +178,70 @@ to the following restrictions:
* What is Kerberos?::
* Building and Installing::
* Setting up a realm::
* Applications::
* Applications::
* Things in search for a better place::
* Kerberos 4 issues::
* Windows 2000 compatability::
* Programming with Kerberos::
* Migration::
* Windows 2000 compatability::
* Programming with Kerberos::
* Migration::
* Acknowledgments::
@detailmenu
--- The Detailed Node Listing ---
Setting up a realm
* Configuration file::
* Creating the database::
* Modifying the database::
* keytabs::
* Serving Kerberos 4/524/kaserver::
* Remote administration::
* Password changing::
* Testing clients and servers::
* Slave Servers::
* Incremental propagation::
* Salting::
* Cross realm::
* Transit policy::
* Setting up DNS::
* Using LDAP to store the database::
* Providing Kerberos credentials to servers and programs::
Applications
* Authentication modules::
* AFS::
Authentication modules
* Digital SIA::
* IRIX::
Kerberos 4 issues
* Principal conversion issues::
* Converting a version 4 database::
* kaserver::
Windows 2000 compatability
* Configuring Windows 2000 to use a Heimdal KDC::
* Inter-Realm keys (trust) between Windows 2000 and a Heimdal KDC::
* Create account mappings::
* Encryption types::
* Authorisation data::
* Quirks of Windows 2000 KDC::
* Useful links when reading about the Windows 2000::
Programming with Kerberos
* Kerberos 5 API Overview::
* Walkthrough of a sample Kerberos 5 client::
* Validating a password in a server application::
* API differences to MIT Kerberos::
@end detailmenu
@end menu
@include intro.texi

6
doc/programming.texi
View File

@@ -1,6 +1,6 @@
@c $Id$
@node Programming with Kerberos
@node Programming with Kerberos, Migration, Windows 2000 compatability, Top
@chapter Programming with Kerberos
First you need to know how the Kerberos model works, go read the
@@ -10,7 +10,7 @@ introduction text (@pxref{What is Kerberos?}).
* Kerberos 5 API Overview::
* Walkthrough of a sample Kerberos 5 client::
* Validating a password in a server application::
* API differences to MIT Kerberos::
* API differences to MIT Kerberos::
@end menu
@node Kerberos 5 API Overview, Walkthrough of a sample Kerberos 5 client, Programming with Kerberos, Programming with Kerberos
@@ -337,7 +337,7 @@ The server is using @manpage{krb5_rd_safe,3} and
See the manual page for @manpage{krb5_verify_user,3}.
@node API differences to MIT Kerberos, , Validating a password in a server application, Programming with Kerberos
@node API differences to MIT Kerberos, , Validating a password in a server application, Programming with Kerberos
@section API differences to MIT Kerberos
This section is somewhat disorganised, but so far there is no overall

46
doc/setup.texi
View File

@@ -4,25 +4,6 @@
@chapter Setting up a realm
@menu
* Configuration file::
* Creating the database::
* Modifying the database::
* keytabs::
* Serving Kerberos 4/524/kaserver::
* Remote administration::
* Password changing::
* Testing clients and servers::
* Slave Servers::
* Incremental propagation::
* Salting::
* Cross realm::
* Transit policy::
* Setting up DNS::
* Using LDAP to store the database::
* Providing Kerberos credentials to servers and programs::
@end menu
A
@cindex realm
realm is an administrative domain. The name of a Kerberos realm is
@@ -30,6 +11,25 @@ usually the Internet domain name in uppercase. Call your realm the same
as your Internet domain name if you do not have strong reasons for not
doing so. It will make life easier for you and everyone else.
@menu
* Configuration file::
* Creating the database::
* Modifying the database::
* keytabs::
* Serving Kerberos 4/524/kaserver::
* Remote administration::
* Password changing::
* Testing clients and servers::
* Slave Servers::
* Incremental propagation::
* Salting::
* Cross realm::
* Transit policy::
* Setting up DNS::
* Using LDAP to store the database::
* Providing Kerberos credentials to servers and programs::
@end menu
@node Configuration file, Creating the database, Setting up a realm, Setting up a realm
@section Configuration file
@@ -529,7 +529,7 @@ automate this you will want to start
Starting the propagation once an hour from @command{cron} is probably a
good idea.
@node Incremental propagation, Salting , Slave Servers, Setting up a realm
@node Incremental propagation, Salting, Slave Servers, Setting up a realm
@section Incremental propagation
There is also a newer, and still somewhat experimental, mechanism for
@@ -640,7 +640,7 @@ the cell name appended to the password.
@end itemize
@node Cross realm, Transit policy , Salting, Setting up a realm
@node Cross realm, Transit policy, Salting, Setting up a realm
@section Cross realm
@cindex Cross realm
@@ -703,7 +703,7 @@ May 3 14:10:54 May 3 23:55:54 host/hummel.it.su.se@@SU.SE
@end example
@node Transit policy, Setting up DNS , Cross realm, Setting up a realm
@node Transit policy, Setting up DNS, Cross realm, Setting up a realm
@section Transit policy
@cindex Transit policy
@@ -986,7 +986,7 @@ Now you can proceed as in @xref{Using LDAP to store the database}.
Heimdal will pick up the Samba LDAP entries if they are in the same
search space as the Kerberos entries.
@node Providing Kerberos credentials to servers and programs, , Using LDAP to store the database, Setting up a realm
@node Providing Kerberos credentials to servers and programs, , Using LDAP to store the database, Setting up a realm
@section Providing Kerberos credentials to servers and programs
Some services require Kerberos credentials when they start to make