Switch branches/tags
ms-bug-test-20060525 krb5-1.16-beta1 krb5-1.15.2-final krb5-1.15.1-final krb5-1.15-final krb5-1.15-beta2 krb5-1.15-beta1 krb5-1.14.6-final krb5-1.14.5-final krb5-1.14.4-final krb5-1.14.3-final krb5-1.14.2-final krb5-1.14.1-final krb5-1.14-final krb5-1.14-beta2 krb5-1.14-beta1 krb5-1.14-alpha1 krb5-1.13.7-final krb5-1.13.6-final krb5-1.13.5-final krb5-1.13.4-final krb5-1.13.3-final krb5-1.13.2-final krb5-1.13.1-final krb5-1.13-final krb5-1.13-beta1 krb5-1.13-alpha1 krb5-1.12.5-final krb5-1.12.4-final krb5-1.12.3-final krb5-1.12.2-final krb5-1.12.1-final krb5-1.12-final krb5-1.12-beta2 krb5-1.12-beta1 krb5-1.12-alpha1 krb5-1.11.6-final krb5-1.11.5-final krb5-1.11.4-final krb5-1.11.3-final krb5-1.11.2-final krb5-1.11.1-final krb5-1.11-final krb5-1.11-beta2 krb5-1.11-beta1 krb5-1.11-alpha1 krb5-1.10.7-final krb5-1.10.6-final krb5-1.10.5-final krb5-1.10.4-final krb5-1.10.3-final krb5-1.10.2-final krb5-1.10.1-final krb5-1.10-final krb5-1.10-beta1 krb5-1.10-alpha2 krb5-1.10-alpha1 krb5-1.9.5-final krb5-1.9.4-final krb5-1.9.3-final krb5-1.9.2-final krb5-1.9.2-beta1 krb5-1.9.1-final krb5-1.9.1-beta1 krb5-1.9-final krb5-1.9-beta3 krb5-1.9-beta2 krb5-1.9-beta1 krb5-1.8.6-final krb5-1.8.5-final krb5-1.8.5-beta1 krb5-1.8.4-final krb5-1.8.3-final krb5-1.8.3-beta1 krb5-1.8.2-final krb5-1.8.2-beta1 krb5-1.8.1-final krb5-1.8.1-beta2 krb5-1.8.1-beta1 krb5-1.8-final krb5-1.8-beta2 krb5-1.8-beta1 krb5-1.8-alpha1 krb5-1.7.2-final krb5-1.7.1-final krb5-1.7.1-beta1 krb5-1.7-final krb5-1.7-beta3 krb5-1.7-beta2 krb5-1.7-beta1 krb5-1.7-alpha1 krb5-1.6.4-beta1 krb5-1.6.3-final krb5-1.6.3-beta2 krb5-1.6.3-beta1 krb5-1.6.2-final krb5-1.6.1-final krb5-1.6.1-beta1 krb5-1.6-final krb5-1.6-beta2
Nothing to show
Find file History
Latest commit e4ffb91 Oct 11, 2017 @greghudson greghudson Fix default enctype order in docs
Commit 4c234d8 added the aes-sha2
enctypes to the documented default enctypes, but in the wrong order.
Reported by Weijun Wang.

ticket: 8616 (new)
target_version: 1.15-next
target_version: 1.16
tags: pullup
Permalink
..
Failed to load latest commit information.
_static Consolidate style settings in kerb.css Jan 31, 2013
_templates Refactor rellinks formatting in layout.html Jan 31, 2013
admin Add --pid-file option to kpropd Sep 22, 2017
appdev Add y2038 documentation May 16, 2017
basic Replace references to OS X Apr 20, 2017
build Remove the NSS PKINIT crypto implementation Mar 27, 2017
ccapi Add documentation for error codes used for flow control Oct 3, 2007
doxy_examples Updated documentation: added usage example for krb5_tkt_creds family,… May 5, 2011
formats Fix keytab file format description Mar 22, 2016
kadm5 Remove adb_policy_init and adb_policy_close Apr 4, 2014
plugindev Add KDC policy pluggable interface Aug 18, 2017
rpc * design.tex: Silly typo fixed Jun 20, 2001
tools Fix minor documentation errors Apr 29, 2015
user Clarify kinit principal selection Sep 28, 2016
README Update doc build instructions Feb 14, 2014
about.rst New section: Contributing to Kerb documentation Jan 31, 2013
build_this.rst Update doc build instructions Feb 14, 2014
coding-style Make doc/coding-style point to wiki page May 22, 2012
conf.py Fix default enctype order in docs Oct 18, 2017
contributing.txt initial draft contribution guidelines Jun 20, 2007
copyright.rst Update copyright years to 2017 Jan 3, 2017
index.rst Add formats section to documentation Feb 27, 2015
iprop-notes.txt some comments from Love Aug 4, 2008
kadm5-errmsg.txt ideas for passing error msg info across kadm5 api Jan 23, 2007
mitK5defaults.rst Remove port 750 from the KDC default ports Mar 24, 2016
mitK5features.rst Replace references to OS X Apr 20, 2017
mitK5license.rst Add copyright footer to HTML docs Dec 17, 2012
notice.rst Replace references to OS X Apr 20, 2017
resources.rst Add web pages to resources.rst Dec 18, 2012
thread-safe.txt Note last real update was a while back; delete listings of libraries … Dec 28, 2009
threads.txt Fixing minorly grammatical bad Dec 28, 2009

README

BUILDING
========

See doc/build_this.rst for details about how to build the
documentation.


CONVENTIONS
===========

We use the following conventions:

* Use four-space indentation where indentation levels are arbitrary.
  Do not use tabs anywhere.  Avoid trailing whitespace at the end of
  lines or files.

* Fill lines to 70 columns (the emacs default) where lines can be
  wrapped.

* For section headers, use === underlines for page titles, --- for
  sections, ~~~ for subsections, and ### for sub-subsections.  Make
  underlines exactly as long as titles.  Do not include trailing
  punctuation in section headers.  Do not capitalize section headers
  (except for the first word) except in source files intended to
  generate man pages.

* For bullet lists, use * for top-level bullets and - for sub-bullets.
  Do not indent bullet or enumerated lists relative to the surrounding
  text.

* Use italics (*word*) for words representing variables or parameters.
  Use boldface (**word**) for command options, subcommands of programs
  like kadmin, and krb5.conf/kdc.conf parameter names.  Use literal
  text (``text``) for examples and multi-component pathnames.  For
  command names, single-component filenames, and krb5.conf/kdc.conf
  section names, use references (like :ref:`kadmin(1)`) if introducing
  them, or just use them unadorned otherwise.

* In man pages for commands with subcommands, make a subsection for
  each subcommand.  Start the subcommand with an indented synopsis,
  then follow with non-indented text describing the subcommand and its
  options.  See kadmin_local.rst for an example.

* In man page synopses, put a newline in the RST source before each
  option.  Put all parts of the synopsis at the same indentation
  level.  Ideally we would want a hanging indent to the width of the
  command or subcommand name, but RST doesn't support that.  Use
  boldface for literal text in the synopsis, italics for variable
  text, and unadorned text for syntax symbols (such as square brackets
  to indicate optional parameters).  If immediately following one kind
  of inline markup with another or putting inline markup next to
  punctuation, you may need to use "\ " as a dummy separator.

* For directives that take a content block (e.g., note, error, and
  warning), leave a blank line before the content block (after any
  arguments or options that may be present).