{"push_id":1041394237,"size":2,"distinct_size":2,"ref":"refs/heads/dev/negotiatestream","head":"61174462fec2e09afa59ade2d16d980a1c464602","before":"52258059c3d0e7a0ade8ca19140d6691b8dfa269","commits":[{"sha":"6104a97cdcc3defa86f4d1b1ec3dfa5f45db2ad1","author":{"email":"a6fd085ae2e7d30036e7cb5eb83a474b9bca197c@microsoft.com","name":"Rahul Kotecha"},"message":"Kerberos sign only interop issue\n\nWhen kerberos is negotiated with Sign Only protection level from *nix\nclient against a windows server, *nix client interpretes the session flags\nas supported and hence always set CONFIDENTIALITY flag irresepective of\nthe requested flags/protection level. This, in windows server which\ninterpretes the flags as required, casues the windows server to expect all\nthe further communication to be encrypted, which is not the case and hence\nserver side processing fails.\nTo override this behaviour, starting MIT Kerberos 1.14 and heimdal\nimplementaion, we need to call gss_set_cred_option with\nGSS_KRB5_CRED_NO_CI_FLAGS_X. When not available, the windows server should\nfail in negotiating Kerberos Sign Only.","distinct":true,"url":"https://api.github.com/repos/dotnet/corefx/commits/6104a97cdcc3defa86f4d1b1ec3dfa5f45db2ad1"},{"sha":"61174462fec2e09afa59ade2d16d980a1c464602","author":{"email":"a6fd085ae2e7d30036e7cb5eb83a474b9bca197c@microsoft.com","name":"Rahul Kotecha"},"message":"Merge pull request #6989 from rahulkotecha/dev/negotiatestream\n\nKerberos sign only interop issue","distinct":true,"url":"https://api.github.com/repos/dotnet/corefx/commits/61174462fec2e09afa59ade2d16d980a1c464602"}]}