krb5.git/doc/admin/database.rst, branch master-mechdconf Unnamed repository; edit this file 'description' to name the repository. Document hierarchical iprop 2014-02-21T02:11:29+00:00 Greg Hudson ghudson@mit.edu 2014-01-28T19:19:33+00:00 e87bba2e8a8c753b761227dda5f2e216a6771db2 Also remove an outdated caveat, but add a new one about policy changes causing full resyncs. ticket: 7855 
Also remove an outdated caveat, but add a new one about policy changes
causing full resyncs.

ticket: 7855
Document master key rollover 2013-10-30T16:58:23+00:00 Greg Hudson ghudson@mit.edu 2013-10-25T16:30:48+00:00 e4b5d426a1e1e00367cc44a9619535ab71b20393 Add a new section to database.rst documenting the procedure for rolling the master key. ticket: 7732 (new) target_version: 1.12 tags: pullup 
Add a new section to database.rst documenting the procedure for
rolling the master key.

ticket: 7732 (new)
target_version: 1.12
tags: pullup
Add a note about how to apply/remove policies 2013-08-16T17:21:25+00:00 Brad Davis brd@FreeBSD.org 2013-08-15T21:39:56+00:00 af0d51a9683c5f71737a5662f156bbb449b2a8a8 Put a note in the the policies section of the documentation for how to apply policies to principals. [kaduk@mit.edu: reformat commit message] ticket: 7693 (new) 
Put a note in the the policies section of the documentation for how to
apply policies to principals.

[kaduk@mit.edu: reformat commit message]

ticket: 7693 (new)
Reformat RST to avoid sphinx warnings 2012-12-10T18:01:07+00:00 Ben Kaduk kaduk@mit.edu 2012-11-28T19:19:43+00:00 8bff1e50c28b6f11b771add7bd7d4a57419a567b Old versions of docutils will see inline markup (e.g., :ref:`foo`) at the beginning of a line in the content of a directive block and attempt to interpret that markup as options or arguments to the directive. RST intended as inline markup (as opposed to modifying the behavior of the directive) will not be interpretable in this context, and causes Sphinx to emit a warning. Work around this behavior by always leaving a blank line before the content of a directive block, forcing it to be interpreted as content and not options or arguments. The buggy behavior was only encountered in note environments, but for consistency of style, also reformat warning and error blocks. Note the new style constraint in doc/README. ticket: 7469 (new) title: doc buildslave generates sphinx warnings tags: pullup target_version: 1.11 
Old versions of docutils will see inline markup (e.g., :ref:`foo`)
at the beginning of a line in the content of a directive block
and attempt to interpret that markup as options or arguments
to the directive.  RST intended as inline markup (as opposed to
modifying the behavior of the directive) will not be interpretable
in this context, and causes Sphinx to emit a warning.

Work around this behavior by always leaving a blank line before
the content of a directive block, forcing it to be interpreted
as content and not options or arguments.

The buggy behavior was only encountered in note environments, but
for consistency of style, also reformat warning and error blocks.

Note the new style constraint in doc/README.

ticket: 7469 (new)
title: doc buildslave generates sphinx warnings
tags: pullup
target_version: 1.11
Cross-reference account lockout documentation 2012-12-05T16:42:55+00:00 Greg Hudson ghudson@mit.edu 2012-12-05T16:42:55+00:00 718868423c7a1e712e54c841b88521e23d374745 Link to the database.rst description of policy objects when talking about them. Briefly mention the "default" policy. Link to the kadmin_local.rst description of policy fields when referencing them. Describe policy fields more briefly, and expand the kadmin_local.rst descriptions where appropriate. ticket: 7480 (new) target_version: 1.11 tags: pullup 
Link to the database.rst description of policy objects when talking
about them.  Briefly mention the "default" policy.  Link to the
kadmin_local.rst description of policy fields when referencing them.
Describe policy fields more briefly, and expand the kadmin_local.rst
descriptions where appropriate.

ticket: 7480 (new)
target_version: 1.11
tags: pullup
Rename doc subdirectories 2012-11-14T20:31:13+00:00 Ben Kaduk kaduk@mit.edu 2012-11-07T03:15:50+00:00 ccaf2682c79974cee368d2f3b0611dabc1361df5 We like these names better, and they match the PDF document filenames. admins -> admin appldev -> appdev users -> user and catch up where the names are used elsewhere. The relay/ directory has been removed, with its contents moved to the top level in build_this.rst and a new about.rst. The section headers for kadmind, krb5kdc, sserver, kpasswd, kswitch, and sclient are misdetected as conflict markers. bigredbutton: whitespace ticket: 7433 tags: pullup 
We like these names better, and they match the PDF document filenames.

admins -> admin
appldev -> appdev
users -> user

and catch up where the names are used elsewhere.

The relay/ directory has been removed, with its contents moved to the
top level in build_this.rst and a new about.rst.

The section headers for kadmind, krb5kdc, sserver, kpasswd, kswitch,
and sclient are misdetected as conflict markers.
bigredbutton: whitespace

ticket: 7433
tags: pullup