payload: {"push_id":3688747787,"size":1,"distinct_size":1,"ref":"refs/heads/ext_rfc4178","head":"ef0f04a15e7cd45c390963b38c0e51730788e5ce","before":"8f77bf70ca09f88e1720b1e4647a6085e914ca95","commits":[{"sha":"ef0f04a15e7cd45c390963b38c0e51730788e5ce","author":{"name":"Changmin Teng","email":"5364987b7f1f5ed09ab0754cfb8a5faf3db96125@redhat.com"},"message":"Implement support for GSSAPI extension RFC 4178\n\nRFC 4178 provides two support API calls that enable the caller to\nmanipulate the set of acceptable security mechanisms used in SPNEGO\nprotocol; for the given credentials, the gss_get_neg_mechs call is\nused to indicate the current set of security mechanisms available\nfor negotiation, and the gss_set_neg_mechs call is used to specify\nthe set of security mechanisms avaiable for negotiation. Since\ngss_get_neg_mechs is not implemented by MIT krb5, we are only\nimplementing the raw interface for the latter call. Note that\nalthough RFC 4178 did not specify that the mech_set argument cannot\nbe an empty set, we are forcing it to be non empty in the low-level\nAPI here since passing an empty set will always trigger an error in\nMIT krb5 implementation.","distinct":true,"url":"https://api.github.com/repos/tengcm2015/python-gssapi/commits/ef0f04a15e7cd45c390963b38c0e51730788e5ce"}]}
other: {"actor":{"display_login":"tengcm2015"}}