[Heimdal-source-changes] [heimdal/heimdal] 51fdb4: krb5: Fix warning in krb5_get_error_string()

[Nico Williams]

  Branch: refs/heads/master
  Home:   https://github.com/heimdal/heimdal
  Commit: 51fdb4bc04a692ea4adffb13f57dcf58197a285f
      https://github.com/heimdal/heimdal/commit/51fdb4bc04a692ea4adffb13f57dcf58197a285f
  Author: Nicolas Williams <nico at twosigma.com>
  Date:   2020-04-26 (Sun, 26 Apr 2020)

  Changed paths:
    M lib/krb5/deprecated.c

  Log Message:
  -----------
  krb5: Fix warning in krb5_get_error_string()


  Commit: 2cb40ed97c92b3c565aa18d97cfbd5f5327bc29c
      https://github.com/heimdal/heimdal/commit/2cb40ed97c92b3c565aa18d97cfbd5f5327bc29c
  Author: Nicolas Williams <nico at twosigma.com>
  Date:   2020-04-26 (Sun, 26 Apr 2020)

  Changed paths:
    M lib/gssapi/sanon/accept_sec_context.c
    M lib/gssapi/sanon/crypto.c
    M lib/gssapi/sanon/export_sec_context.c
    M lib/gssapi/sanon/init_sec_context.c
    M lib/gssapi/sanon/inquire_context.c
    M lib/gssapi/sanon/negoex.c
    M lib/gssapi/sanon/sanon_locl.h

  Log Message:
  -----------
  sanon: Fix flags and ctx export/import confusion

We were passing SANON flags to _gss_mg_import_rfc4121_context(), which
wants GSS flags.  Meanwhile, I broke gss_inquire_context() on imported
SAnon contexts when I did my review of SAnon.

This commit fixes both issues and removes SANON_FLAG_*, which were only
ever needed because of a flag to track whether a context was locally
initiated or accepted.  Now we use a separate int field of the sanon_ctx
to track whether a context was locally initiated.  Once an SAnon context
is fully established, we rely on gss_inquire_context() on the rfc4121
sub-context for all metadata that isn't the initiator and acceptor names
nor the mechanism OID.


Compare: https://github.com/heimdal/heimdal/compare/5057d04f6a47...2cb40ed97c92