It seems to be "more correct".
# base URL from which the finished HTML is served.
#html_use_opensearch = ''
-# This is the file name suffix for HTML files (e.g. ".xhtml").
+# This is the file name suffix for HTML files (e.g., ".xhtml").
#html_file_suffix = None
# Output file base name for HTML help builder.
principal should have. If this matches, then a string will be
formed from *string*, substituting the realm of the principal
for ``$0`` and the *n*'th component of the principal for
- ``$n`` (e.g. if the principal was ``johndoe/admin`` then
+ ``$n`` (e.g., if the principal was ``johndoe/admin`` then
``[2:$2$1foo]`` would result in the string
``adminjohndoefoo``). If this string matches *regexp*, then
the ``s//[g]`` substitution command will be run over the
Principal aliases are only returned by the KDC when the client
requests canonicalization. Canonicalization is normally requested for
service principals; for client principals, an explicit flag is often
-required (e.g. ``kinit -C``) and canonicalization is only performed
+required (e.g., ``kinit -C``) and canonicalization is only performed
for initial ticket requests.
true for historical reasons only.
If you anticipate users frequently logging into remote hosts
-(e.g. using ssh) using forwardable credentials, consider setting
+(e.g., using ssh) using forwardable credentials, consider setting
**forwardable** to true so that users obtain forwardable tickets by
default. Otherwise users will need to use ``kinit -f`` to get
forwardable tickets.
Add administrators to the Kerberos database
-------------------------------------------
-Next you need to add administrative principals (i.e. principals who
+Next you need to add administrative principals (i.e., principals who
are allowed to administer Kerberos database) to the Kerberos database.
You *must* add at least one principal now to allow communication
between the Kerberos administration daemon kadmind and the kadmin
Use *FLAGS* as the default set of C compiler flags.
**CPP=**\ *CPP*
- C preprocessor to use. (e.g. ``CPP='gcc -E'``)
+ C preprocessor to use. (e.g., ``CPP='gcc -E'``)
**CPPFLAGS=**\ *CPPOPTS*
Use *CPPOPTS* as the default set of C preprocessor flags. The
**LDFLAGS=**\ *LDOPTS*
This option informs the linker where to get additional libraries
- (e.g. ``-L<lib dir>``).
+ (e.g., ``-L<lib dir>``).
**LIBS=**\ *LDNAME*
This option allows one to specify libraries to be passed to the
- linker (e.g. ``-l<library>``)
+ linker (e.g., ``-l<library>``)
**SS_LIB=**\ *libs*...
If ``-lss`` is not the correct way to link in your installed ss
**--build=**\ *BUILD*
Configure for building on *BUILD*
- (e.g. ``--build=x86_64-linux-gnu``).
+ (e.g., ``--build=x86_64-linux-gnu``).
**--host=**\ *HOST*
Cross-compile to build programs to run on *HOST*
- (e.g. ``--host=x86_64-linux-gnu``). By default, Kerberos V5
+ (e.g., ``--host=x86_64-linux-gnu``). By default, Kerberos V5
configuration will look for "build" option.
-----------------
**--with-**\ *PACKAGE*\ [=ARG\]
- Use *PACKAGE* (e.g. ``--with-imap``). The default value of *ARG*
+ Use *PACKAGE* (e.g., ``--with-imap``). The default value of *ARG*
is ``yes``.
**--without-**\ *PACKAGE*
Do not use *PACKAGE* (same as ``--with-PACKAGE=no``)
- (e.g. ``--without-libedit``).
+ (e.g., ``--without-libedit``).
**--with-size-optimizations**
Enable a few optimizations to reduce code size possibly at some
should return only vague error codes to clients.
**--with-crypto-impl=**\ *IMPL*
- Use specified crypto implementation (e.g. **--with-crypto=**\
+ Use specified crypto implementation (e.g., **--with-crypto=**\
*openssl*). Default is a native MIT Kerberos implementation
``builtin``. The other currently implemented crypto backends are
``openssl`` and ``nss``. (See :ref:`mitK5features`)
=============
It is considered good practice to develop and maintain the test suite
-with high level of test coverage, i.e. the tests that execute every
+with high level of test coverage, i.e., the tests that execute every
single statement, every line of the code and then validate the result.
The GNU's gcov is a tool that analyses the frequency of execution of
A basic read-only profile module need only implement the
**get_values** and **free_values** methods. The **get_values** method
-accepts a null-terminated list of C string names (e.g. an array
+accepts a null-terminated list of C string names (e.g., an array
containing "libdefaults", "clockskew", and NULL for the **clockskew**
variable in the :ref:`libdefaults` section) and returns a
null-terminated list of values, which will be cleaned up with the
.. note:: For the sake of clarity, all references to and attributes of
the user invoking the program will start with "source"
- (e.g. "source user", "source cache", etc.).
+ (e.g., "source user", "source cache", etc.).
Likewise, all references to and attributes of the target
account will start with "target".
To fulfill the first mission, ksu operates in two phases:
authentication and authorization. Resolving the target principal name
is the first step in authentication. The user can either specify his
-principal name with the **-n** option (e.g. ``-n jqpublic@USC.EDU``)
+principal name with the **-n** option (e.g., ``-n jqpublic@USC.EDU``)
or a default principal name will be assigned using a heuristic
described in the OPTIONS section (see **-n** option). The target user
name must be the first argument to ksu; if not specified root is the
default. If ``.`` is specified then the target user will be the
-source user (e.g. ``ksu .``). If the source user is root or the
+source user (e.g., ``ksu .``). If the source user is root or the
target user is the source user, no authentication or authorization
takes place. Otherwise, ksu looks for an appropriate Kerberos ticket
in the source cache.
**-c** *source_cache_name*
- Specify source cache name (e.g. ``-c FILE:/tmp/my_cache``). If
+ Specify source cache name (e.g., ``-c FILE:/tmp/my_cache``). If
**-c** option is not used then the name is obtained from
**KRB5CCNAME** environment variable. If **KRB5CCNAME** is not
defined the source cache name is set to ``krb5cc_<source uid>``.
ksu attempts to get a ticket for the end server just as Kerberized
telnet and rlogin. Thus, there must be an entry for the server in the
-Kerberos database (e.g. ``host/nii.isi.edu@ISI.EDU``). The keytab
+Kerberos database (e.g., ``host/nii.isi.edu@ISI.EDU``). The keytab
file must be in an appropriate location.
projects / thirdparty / krb5.git / commitdiff
