[
https://issues.apache.org/jira/browse/HTTPCLIENT-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838304#action_12838304
]
Karl Wright commented on HTTPCLIENT-919:
----------------------------------------
I raised this specific issue on [email protected] yesterday, and
received the following response from William A. Rowe, Jr.:
>>>>>>
AIUI - this is probably covered under the interop/Microsoft patent pledge.
If it is not, asking them to make it explicitly so might not be a big issue.
See
http://www.microsoft.com/openspecifications/programs/wspp/wspp-patents/wspp-patent-pledges/
and
related documents.
<<<<<<
The document in question apparently pledges to protect open-source developers
and their community against direct patent-infringement lawsuits for certain
areas of their IP, including protocol specifications as described in this
document:
http://www.microsoft.com/openspecifications/programs/wspp/wspp-patents/
The patents that Microsoft licenses are described by protocol in the following
document:
http://download.microsoft.com/download/1/0/4/1041AEF2-0ABC-4D48-A909-EC3CD52A7F13/WSPP_Patent_Mapping.pdf
That document explicitly mentions NTLM as being a Microsoft protocol, but
asserts no patent claims against it.
So if I read this correctly:
(1) Open source developers are not subject to patent claims by Microsoft in any
case, and
(2) Microsoft asserts no patent claims whatsoever against NTLM, and does not
suggest patent licensing for native implementations of such even against
for-profit corporations.
I will, of course, post any further responses that appear from legal-discuss.
> NTLM implementation lacks support for NTLMv1, NTLMv2, and NTLM2 Session forms
> of NTLM
> -------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-919
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-919
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpAuth
> Reporter: Karl Wright
> Fix For: Future
>
> Attachments: ntlmv2-etc.patch
>
>
> The current HttpClient implementation lacks support for all enhancements to
> NTLM after Windows 95. That includes NTLMv1, NTLMv2, and NTLM2 Session
> Response varieties of the protocol.
> This seriously impacts the usability of HttpClient in enterprise situations,
> which has required the Lucene Connector Framework team to extend HttpClient
> to address the issue.
> I've attached a patch which contains the implementation used by LCF.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
