@c definitions added by jcb.
@c %**start of header
@c guide
-@setfilename kerbnet-admin.info
-@settitle Kerb*Net System Administrator's Guide
+@setfilename kerberos-admin.info
+@settitle Kerberos V5 System Administrator's Guide
@c @setchapternewpage odd @c chapter begins on next odd page
@setchapternewpage on @c chapter begins on next page
@smallbook @c Format for 7" X 9.25" paper
@end iftex
@include definitions.texinfo
-@set EDITION 0.9 beta
+@set EDITION b6-1
@finalout @c don't print black warning boxes
@c is:
@c
@c @node New Section Name
-
@c @section New Section Name
@c
@c M-x texinfo-every-node-update will take care of calculating the
* Updates::
* Backups of Secure Hosts::
* Support::
+* Bug Reporting::
* Appendix::
@end menu
@node Introduction, How Kerberos Works, Top, Top
@chapter Introduction
+@ifset CYGNUS
Congratulations on your purchase of @value{PRODUCT}. @value{COMPANY}
believes @value{PRODUCT} provides the best network security available.
Please let us know if we can be of assistance in getting your
installation of @value{PRODUCT} set up and running.
+@end ifset
@menu
* Why Should I use Kerberos?::
This will have to wait until the next release. *sigh*
@end ignore
+@ifset CYGNUS
@node Updates, Backups of Secure Hosts, Application Servers, Top
@chapter Updates
Other than any functionality changes in the programs, the upgrade should
be completely user-transparent.
@c Reference to upgrading from Kerberos V4 document, once it's written.
+@end ifset
@node Backups of Secure Hosts, Support, Updates, Top
@chapter Backups of Secure Hosts
@node Backing Up the Kerberos Database, , Backups of Secure Hosts, Backups of Secure Hosts
@section Backing Up the Kerberos Database
-It is possible that the Kerberos database could be corrupted. If this
-happens on one of the slave KDCs, you might never notice, since the next
-automatic propagation of the database would install a fresh copy.
-However, if it happens to the master KDC, the corrupted database would
-be propagated to all of the slaves during the next propagation. For
-this reason, @value{COMPANY} recommends that you back up your Kerberos
-database regularly. Because the master KDC is continuously dumping the
-database to a file in order to propagate it to the slave KDCs, it is a
-simple matter to have a cron job periodically copy the dump file to a
-secure machine elsewhere on your network. (Of course, it is important
-to make the host where these backups are stored as secure as your KDCs,
-and to encrypt its transmission across your network.) Then if your
-database becomes corrupted, you can load the most recent dump onto the
-master KDC. (@xref{Restoring a Kerberos Database from a Dump File}.)
-
-@node Support, Appendix, Backups of Secure Hosts, Top
+As with any file, it is possible that your Kerberos database could
+become corrupted. If this happens on one of the slave KDCs, you might
+never notice, since the next automatic propagation of the database would
+install a fresh copy. However, if it happens to the master KDC, the
+corrupted database would be propagated to all of the slaves during the
+next propagation. For this reason, @value{COMPANY} recommends that you
+back up your Kerberos database regularly. Because the master KDC is
+continuously dumping the database to a file in order to propagate it to
+the slave KDCs, it is a simple matter to have a cron job periodically
+copy the dump file to a secure machine elsewhere on your network. (Of
+course, it is important to make the host where these backups are stored
+as secure as your KDCs, and to encrypt its transmission across your
+network.) Then if your database becomes corrupted, you can load the
+most recent dump onto the master KDC. (@xref{Restoring a Kerberos
+Database from a Dump File}.)
+
+@ifset CYGNUS
+@node Support, Bug Reporting, Backups of Secure Hosts, Top
@chapter Support
@menu
@section Using sendpr
@include send-pr.texinfo
-
-@node Appendix, , Support, Top
+@end ifset
+
+@ifset MIT
+@node Bug Reporting, Appendix, Support, Top
+@chapter Bug Reporting
+
+In any complex software, there will be bugs. Please send bug reports or
+other problems you may uncover to the e-mail address
+@b{krb5-bugs@@mit.edu}. Please mention which version of the Kerberos V5
+distribution you are using, and whether you have made any private
+changes. Bug reports that include proposed fixes are especially
+welcome. If you do include fixes, please send them using either context
+diffs or unified diffs (using @samp{diff -c} or @samp{diff -u},
+respectively).
+@end ifset
+
+@node Appendix, , Bug Reporting, Top
@appendix Appendix
@menu
\input texinfo @c -*-texinfo-*-
@c %**start of header
@c guide
-@setfilename KerbNet-User.info
-@settitle Kerb*Net UNIX User's Guide
+@setfilename kerberos-user.info
+@settitle Kerberos V5 UNIX User's Guide
@setchapternewpage odd @c chapter begins on next odd page
@c @setchapternewpage on @c chapter begins on next page
@smallbook @c Format for 7" X 9.25" paper
@end iftex
@include definitions.texinfo
-@set EDITION 0.9 beta
+@set EDITION b6-1
@finalout @c don't print black warning boxes
@c comand before each @section or @subsection! All you need to enter
@c is:
@c
-
@c @section New Section Name
@c
@c M-x texinfo-every-node-update will take care of calculating the
On many systems, Kerberos is built into the login program, and you get
tickets automatically when you log in. Other programs, such as
-@code{rsh}, @code{rcp}, @code{telnet}, and @code{rlogin}, can forward
+/@code{rsh}, @code{rcp}, @code{telnet}, and @code{rlogin}, can forward
copies of your tickets to the remote host. Most of these programs also
automatically destroy your tickets when they exit. However,
@value{COMPANY} recommends that you explicitly destroy your Kerberos
projects / krb5.git / commitdiff