Commit d3356bc42191c1896ab06835a2fb245e00471420 (ticket 8927)
incorrectly tagged tMERIDIAN as <Number>.  So while the lexer assigns
meridian values to the Meridian union field, the parser erroneously
reads them from the Number field.  On 64-bit IBM zSystems (s390x),
this can result in using the most recently read number as a meridian
value, leading to an abort in ToSeconds().

Fix the tMERIDIAN token type to be <Meridian>.

[ghudson@mit.edu: edited commit message]

ticket: 9087 (new)
tags: pullup
target_version: 1.20-next

Command-line options are described in the following places:

- .rst file "SYNOPSIS" section
- .rst file "OPTIONS" section
- parameters to getopt()
- results of getopt() that are actually handled
- a usage() or xusage() function
- occasionally, a long form in usage()/xusage()
- occasionally, libss subcommand specifications

Over time, these have drifted.  Make an effort to correct this drift,
marking deprecated options as such.  For consistency, remove mention
of long arguments that have an equivalent short form.

ticket: 8987 (new)
tags: pullup
target_version: 1.19-next

In configure.ac and aclocal.m4, eliminate the use of old macros that
will generate warning from the forthcoming autoconf 2.70 release.
Specifically:

* Use AS_HELP_STRING instead of AC_HELP_STRING.

* Use AC_{COMPILE,LINK,RUN}_IFELSE and AC_LANG_{SOURCE,PROGRAM}
instead of AC_TRY_COMPILE and similar.

* Use m4_foreach_w instead of ac_foreach.

* Eliminate AC_PROG_LEX and yylineno checking, as we no longer use
  lex.

* As recommended by autoconf, assume that signal handlers return void
  as specified in C89.

* As recommmended by autoconf, assume <time.h> is present and that
  <sys/time.h>, if present, can be included alongside it.

* Don't call AC_CHECK_FUNCS with a shell variable for the thread
  safety checks.  Instead just assume (as is currently the case) that
  all of the functions have been previously checked.

Bison 3.5 adds a POSIX yacc compliance warning that %type should only
be applied to non-terminals.  Use %token for terminals in getdate.y.
Reported by Norm Green.

ticket: 8927

Correct comment spelling errors detected using codespell.
Reported by Jens Schleusener.

Not having policy defined is a normal occurrence.  While it's a useful
message to log in case it's unexpected, the current form is
unnecessarily alarmist.

ticket: 8857 (new)

Add a table of unsupported enctype numbers to enctype_util.c and
consult it in krb5_enctype_to_name().  Treat unsupported enctype
numbers as deprecated in krb5int_c_deprecated_enctype().  In kadmin,
display "UNSUPPORTED:" before invalid enctype names.

ticket: 8808

The checks for missing option arguments were dead code, because the
loop condition requires at least two remaining arguments.  Instead
check for at least one argument with a leading "-", and check for too
many or too few arguments after the loop.  Add an initial message for
unrecognized options.

[ghudson@mit.edu: adjusted logic to improve mesages in more cases]

Preface ETYPE_DEPRECATED enctypes with "DEPRECATED:" in klist output,
KDC logs, and kadmin interactions.  Also complain in krb5kdc when the
stash file has a deprecated enctype or a deprecated enctype is
requested with -k.

ticket: 8773 (new)

ticket: 8738 (new)