"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "doc/admin/troubleshoot.rst" between
krb5-1.16.3.tar.gz and krb5-1.17.tar.gz

About: Kerberos is a network authentication protocol. It is designed to provide strong authentication for client/server applications by using secret-key cryptography (MIT implementation). Current release.

troubleshoot.rst  (krb5-1.16.3):troubleshoot.rst  (krb5-1.17)
skipping to change at line 105 skipping to change at line 105
appear in trace_logging_ output from :ref:`kinit(1)` or, starting in appear in trace_logging_ output from :ref:`kinit(1)` or, starting in
release 1.12, as an error message from kinit or another program which release 1.12, as an error message from kinit or another program which
gets initial tickets. The error message is more likely to appear gets initial tickets. The error message is more likely to appear
properly on the client if the principal entry has no long-term keys. properly on the client if the principal entry has no long-term keys.
.. _kprop_no_route: .. _kprop_no_route:
kprop: No route to host while connecting to server kprop: No route to host while connecting to server
.................................................. ..................................................
Make sure that the hostname of the slave (as given to kprop) is Make sure that the hostname of the replica KDC (as given to kprop) is
correct, and that any firewalls between the master and the slave allow correct, and that any firewalls between the master and the replica
a connection on port 754. allow a connection on port 754.
.. _kprop_con_refused: .. _kprop_con_refused:
kprop: Connection refused while connecting to server kprop: Connection refused while connecting to server
.................................................... ....................................................
If the slave is intended to run kpropd out of inetd, make sure that If the replica KDC is intended to run kpropd out of inetd, make sure
inetd is configured to accept krb5_prop connections. inetd may need that inetd is configured to accept krb5_prop connections. inetd may
to be restarted or sent a SIGHUP to recognize the new configuration. need to be restarted or sent a SIGHUP to recognize the new
If the slave is intended to run kpropd in standalone mode, make sure configuration. If the replica is intended to run kpropd in standalone
that it is running. mode, make sure that it is running.
.. _kprop_sendauth_exchange: .. _kprop_sendauth_exchange:
kprop: Server rejected authentication (during sendauth exchange) while authentic ating to server kprop: Server rejected authentication (during sendauth exchange) while authentic ating to server
................................................................................ ............... ................................................................................ ...............
Make sure that: Make sure that:
#. The time is synchronized between the master and slave KDCs. #. The time is synchronized between the master and replica KDCs.
#. The master stash file was copied from the master to the expected #. The master stash file was copied from the master to the expected
location on the slave. location on the replica.
#. The slave has a keytab file in the default location containing a #. The replica has a keytab file in the default location containing a
``host`` principal for the slave's hostname. ``host`` principal for the replica's hostname.
 End of changes. 4 change blocks. 
9 lines changed or deleted 9 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)