Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implemented RFC 4178 extension #176

Merged
merged 1 commit into from
Jul 8, 2019

Commits on Jun 24, 2019

  1. Implement support for GSSAPI extension RFC 4178

    RFC 4178 provides two support API calls that enable the caller to
    manipulate the set of acceptable security mechanisms used in SPNEGO
    protocol; for the given credentials, the gss_get_neg_mechs call is
    used to indicate the current set of security mechanisms available
    for negotiation, and the gss_set_neg_mechs call is used to specify
    the set of security mechanisms avaiable for negotiation. Since
    gss_get_neg_mechs is not implemented by MIT krb5, we are only
    implementing the raw interface for the latter call. Note that
    although RFC 4178 did not specify that the mech_set argument cannot
    be an empty set, we are forcing it to be non empty in the low-level
    API here since passing an empty set will always trigger an error in
    MIT krb5 implementation.
    tengcm2015 committed Jun 24, 2019
    Configuration menu
    Copy the full SHA
    1dcb5b9 View commit details
    Browse the repository at this point in the history