<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/libgit2.git/src/libgit2/transports/auth_gssapi.c, branch main</title>
<subtitle>github.com: libgit2/libgit2.git
</subtitle>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/libgit2.git/'/>
<entry>
<title>http: refactor GSSAPI / negotiate / NTLM auth</title>
<updated>2023-03-21T09:14:06+00:00</updated>
<author>
<name>Edward Thomson</name>
<email>ethomson@edwardthomson.com</email>
</author>
<published>2023-03-11T08:03:34+00:00</published>
<link rel='alternate' type='text/html' href='http://91.123.203.49/cgit/delta/libgit2.git/commit/?id=cff0d9b1cc2432ab6a6eab777cdfe230ee07fca1'/>
<id>cff0d9b1cc2432ab6a6eab777cdfe230ee07fca1</id>
<content type='text'>
Name the GSSAPI and ntlmclient authentication providers as such. Today
they're named after the authentication mechanism ("Negotiate", "NTLM")
instead of their implementation.

If we have competing implementations for the same mechanism (eg, a
future Windows SSPI-based provider for Negotiate and NTLM) then this
will get confusing.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Name the GSSAPI and ntlmclient authentication providers as such. Today
they're named after the authentication mechanism ("Negotiate", "NTLM")
instead of their implementation.

If we have competing implementations for the same mechanism (eg, a
future Windows SSPI-based provider for Negotiate and NTLM) then this
will get confusing.
</pre>
</div>
</content>
</entry>
</feed>
