Has anyone gotten negotiable authentication to work with git over http using mod_auth_kerb on the server end? I am unable to get a git client to function correctly in this scenario. I am defining "correctly" as the following: When a valid kerberos ticket is available, use that without prompting for credentials. If for some reason that fails, prompt for credentials and try again using HTTP basic auth. If no valid kerberos ticket is available, prompt for credentials and try using HTTP basic auth. So far the behavior I have been able to reproduce: When 'KrbMethodNegotiate off' is set on the server, the git client will always prompt for username and password and use them. This is very intuitive from the user perspective, but does not take advantage of the kerberos ticket for single sign-on. When 'KrbMethodNegotiate on' is set on the server, the git client will always prompt for username and password, but ignore them. If a valid kerberos ticket is available, the command will complete after any arbitrary text is entered into the username and password prompts. If a valid kerberos ticket is not available, the command will fail even if the correct username and password is entered. Using some combinations of various git and curl versions and compile options will not even get that far, and respond immediately with a 401. I have tried several different versions of git, including the latest 1.7.4. I have tried several different versions of curl, including the latest 7.12.3. I have tried several different curl compile-time configuration options, including --with-spenego (using fbopenssl) and --with-gssapi. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html